Docker
Runtimes
The unit of deployment everywhere, the same image runs locally and in production.
A container runtime that packages a process with its filesystem and dependencies, so the same image runs identically wherever the runtime exists.
How we use it
The unit of deployment everywhere here. The same manifest that describes a system produces a local compose stack and the production one, so the difference between a developer machine and a server is the overlay, not the image.
18
systems
Case studies using this
Retail ERP and Point of Sale with Fiscal Integration
A complete single-store retail platform: stock ledger, supplier receipts, sales, and a point of sale that prints legally valid fiscal receipts on certified hardware.
ForkTex Cloud, Declarative Deployment
Our own deployment platform: one manifest describes a system, and the platform provisions it, routes it, secures it, and cuts traffic over without downtime.
Field Assessment and Reporting for Livestock Operations
Two years of full-stack maintenance and feature delivery on a government-integrated field assessment platform. Plus the infrastructure work that kept it running.
Core Platform Engineering for a Carbon-Markets Business
Migrating a carbon-markets platform off a legacy content system onto typed, tested services. Market data, pricing, emissions ingestion, and the operator tooling around them.
Articles about this
Start Any Platform From Scratch
A new engineer should reach a running system with one command, on any of our projects, without reading a wiki page that went stale eight months ago.
Declarative Production
A repository should state how it runs in one file a machine can read. Otherwise every consumer of that fact re-derives it, and one of them is wrong.
Receipts That Satisfy the Law
A fiscal receipt is valid or it is not. There is no partial credit, and the device, not your software, is the authority.