A warehouse management system that deploys in days, not years. Built for the warehouse still run out of spreadsheets, and for the 3PL carrying a system nobody left instructions for. An AI agent configures it — not a consulting team — because every feature is metadata, not code.
No WMS team, and no appetite for a six-month project. Either there is no system at all and the warehouse lives in Excel and in people's heads, or there is one — written years ago, by someone who has left, and nobody dares touch it.
Quark is early. There are places where a system with twenty years of scar tissue is still the right answer, and we would rather you heard that here than three months into an evaluation.
Upload a photo of your aisles. Drop in your stock list as Excel. Describe — in your own words — what you store, how you receive, who picks. The agent extracts zones, SKUs, lot policies and team structure automatically.
The agent's configuration arrives as a draft version of the module — never as a change to your running system. You open it in the Studio and inspect it as a graph: business objects, forms, roles, navigation, rules. Apply when it's right, discard when it isn't. No SQL, no source code, no consultant‑in‑the‑middle.
RF terminals scan their first pallet. Pickers walk their first wave. Every change you make from this moment forward goes through the same Draft → Validate → Approve → Apply pipeline — including the ones the AI proposes itself.
Forms, workflows, validation rules, navigation, business objects — all rows in a database. Not source files. An agent issues INSERT/UPDATE statements; not merge requests.
Endpoints, objects, UI elements expose machine‑readable schemas through introspection. Agents discover new capabilities the moment they exist — no client update, no integration work.
No write goes direct to a live system. Every change passes Draft → Validate → Apply as a new version. The version that was live before it stays. Rollback as a structural property, not a recovery procedure.
Deletions, financial transactions, customer‑facing publishes — they cannot reach execution without an approval signal. Not a configurable option. A code path that physically does not exist.
A field script can read a field. It cannot call the database. It cannot make HTTP. The sandbox isn't a scanner looking for dangerous calls — it's an architecture that refuses to expose the APIs at all.
External governance is only as strong as its perimeter. Quark embeds governance into the primary data model. Change, validation and rollback are not enforced from outside — they are the only available vocabulary for mutation.
read the full manifesto →Today, implementing Infor or SAP eats six months of your team mapping SKUs, drawing zones and writing printer scripts. Clients consider it "included." Your margin lives in the leftover hours.
With Quark, that work takes two weeks. The remaining 5.5 months become available for the work you actually enjoy — process consulting, ERP integration, operator training, new clients.
Compliance does not relax because AI is in the loop — it tightens. Quark's approval hooks, audit logs, and reversible mutations are designed for environments where every change must be justified, attributable, and traceable.
Metadata core. The fundamental particles of warehouse operations — entities, policies, rules.
Voice layer over your WMS. The quantum of sound — listens, confirms, scans, posts back. Stays on SAP, Manhattan, Infor, Odoo. Two-week integration, not a rip-and-replace.
Binds Quark to ERP, marketplaces, carriers, EDI. The strong force between systems.
Carries every state change — receipt, ship, adjust — across modules. Pub/sub with audit.
Lightweight client for RF scanners, tablets, mobiles. Runs everywhere, weighs nothing.
Pre-composed industry templates — 3PL × Pharma, D2C × Fashion. Quarks bound by an industry.
The intelligence hidden in voice sessions. Per-operator acoustic tuning, slotting hints, fraud signals.
The onboarding agent. Carries information at the speed of light.
Reporting that passes through everything — almost weightless, never blocking.
RBAC and identity. Pauli's principle — every user is unique.
Gives meaning — the configuration field that makes other particles real.
Composite adapters — bridges between protocols, formats, eras.
A note on the name — Quark is pronounced [kwɔːk], after Gell-Mann's coinage. He took the spelling from a single line in Joyce's Finnegans Wake: "Three quarks for Muster Mark." Mark is also the name of my son. The metaphor and the family — they earn their place.
I built Quark because I kept watching the same thing happen: a warehouse that knows exactly how it wants to work, and a system that will not let it, until somebody bills six months to change two columns on a form. The problem was never the consultants. It was an architecture where every business rule is code, and code is expensive to touch.
So Quark keeps its features in tables instead — forms, rules, roles, navigation, statutory documents. That one decision is what makes a day-long deployment possible, and it is also what lets an AI agent operate the system without being trusted, because every change it proposes arrives as a draft that a person applies or discards.
It is named after the particle, which Gell-Mann named after a line in Finnegans Wake — three quarks for Muster Mark. Mark is my son.
On jurisdictions. Statutory forms and languages are metadata here, not release engineering — which is why TORG‑2, M‑4, M‑11 and INV‑3 ship in the box, and why a new country is a configuration rather than a release. If your paperwork is not in that list yet, adding it is metadata work, not a roadmap item.
We're onboarding the first warehouses now. Leave your email and tell us what you run — we'll reach out the moment your industry template is ready.
Leave your email and we will ask for two things: a spreadsheet of your SKUs and a photo of your aisles. We configure a warehouse from them and show you the result — before you commit to anything, and at no cost.