Skip to main content

What is Quantum?

Quantum is three Go products that work together, plus the piece that keeps them working together:

  • Nucleus — an MVC/REST web framework built on the standard library (net/http, database/sql, log/slog). It is the host: your application is a Nucleus app, and the other two plug into it.
  • Quark — a type-safe ORM for six SQL engines (PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle). It is the data layer — and the one pillar that also works completely on its own, in any Go app, with no trace of the other two.
  • Orbit — an admin panel that mounts in-process into a Nucleus app: browse and edit your models, watch requests and SQL live, manage sessions and access control. One dependency, one Mount(...) call, no sidecar.

The fourth piece is not a product but a promise: a certified set — a trio of versions of the three products that were tested together and published as one manifest. You install the set, not three guesses. More on that here.

Who mounts on whom​

Quantum — a certified set: three versions tested togetheryour Go application — one process, one binaryNucleusweb framework — the hostrouting · modules · auth · CLIOrbitadmin panel — Data Studio,live feed, sessions, RBACmounts in-processQuark — ORM, the data layerSQL databaseQuark also works on its own, in any Go app — no Nucleus, no Orbit.Orbit requires Nucleus. Nucleus requires neither.versions.yaml — the manifest that pins the set

The only hard dependency between products is Orbit → Nucleus. Quark is independent; Nucleus has its own SQL-first data layer (pkg/db + pkg/model), so even inside a Nucleus app, Quark is a choice, not a requirement — here is how to choose.

Where do I start?​

You want…Start with
Just a data layer for any Go appQuark's getting started — no framework involved
A web applicationNucleus's quickstart — add Quark and Orbit later if you want them
To see the whole suite workingThe suite quickstart — one command writes all three pillars wired; five commands in total

When not to use the suite​

Honest boundaries save everyone time:

  • You already have a framework you like. Quark still works for you — it is a standalone ORM. Nucleus and Orbit are not for you.
  • You want an admin panel for a non-Nucleus app. Orbit only mounts on Nucleus. There is no standalone Orbit.
  • You need NoSQL. Quark is relational only, and Nucleus's data layer is database/sql. Six SQL engines, zero document stores.
  • You need a large ecosystem of third-party packages. These are three products from a small project. Beyond them, nucleus add installs the 14 optional modules the project publishes itself — database drivers, telemetry exporters, object storage, an LDAP backend, a secrets resolver, an error reporter and a SAML sign-in provider, each certified with the set — and wires 6 capabilities that are part of the framework itself; there is no registry of third-party plugins. Why Quantum compares the suite with frameworks that have one, and says where they are ahead.

Still here? The quickstart is five commands, then a read of the files they wrote.