A foundation should be yours to read, run and keep.
The systems every product needs: identity, tenancy, billing, messaging, and more. Built to work together from the start. So we refuse to ship anything you have to take on faith. Three verbs, and each one has a mechanism under it rather than a promise.
The ledger schema, the row-level policies and the rounding ship inside the package. Fetch it and read the mechanism before you trust it, rather than taking a sentence about correctness on faith.
Libraries in your own process, on the database you already operate. Nothing calls back to QuxKit at runtime, so there is no service of ours between your product and its data.
Switch the payment or mail provider without a rewrite. Leaving QuxCloud means running the same code somewhere else, which is a migration you control rather than a contract you escape.
It all works. Until the day you need to read it, or leave it.
Every API call, seat and gigabyte becomes revenue you can count on: metered accurately, priced to the cent and reconciled to the penny, from your first customer to your millionth. And you keep all of it: no revenue cut, no platform to rent, no billing team to hire.
One customer never sees another’s data, not because you remembered a filter, but because the boundary is enforced underneath every query. Teams, roles and invitations included, over the same database connection your app already has.
Explore tenant-kit
Everything behind a login. Sign-up, sign-in, email verification, password reset, as a library you embed rather than a service you rent. Secure by default, sessions you can end instantly, one account id the whole family shares. It already runs this site.
Revoke is soft: the row stays for the audit trail and never resolves again.
It remembers how you work, and it knows the code on your machine, and it answers using both at once, instead of asking you to explain yourself again every morning. Open source, and it runs on your computer: your memory stays yours.
Explore ai-member
A full CRM and HR platform: leads to invoices, projects to tickets, people to payroll: built from the very same kits you can pick up and use yourself. Proof that the family composes into something real, and a product you can run today. Open-source core, a managed Cloud, and native mobile apps.
Explore QuxKit CRM
Transactional email you own end to end. Your sending domains, your reputation, your logs, and the record of everything you ever sent. Send through whichever provider suits you today and switch when it stops suiting you, without handing any of that to a platform sitting in the middle of your customers and you.
Explore mail-kitThis is UI-Kit running in your browser, not a video of it. Every ramp step, both modes and every contrast pair are regenerated on the spot. The same engine the rest of the family is drawn with, and the same section that runs on its own page.
Try it
Not a preview pane. The page. Every component, both modes, all eleven ramp steps and every contrast pair are regenerated in the browser, because the generator has no dependencies and no build step to hide behind.
success+6.4° from canonicalwarning-10° from canonicaldanger-4° from canonicalinfo+2.9° from canonical| Role | Light | Dark | Lc | Target |
|---|---|---|---|---|
fg-default | #17191e | #f2f3f6 | 104.4 | 90 |
fg-muted | #55585e | #ccced2 | 84.8 | 75 |
fg-subtle | #7d8086 | #b2b4b9 | 66.9 | 60 |
fg-on-accent | #fdfdff | #fdfdff | 93.9 | 75 |
fg-accent | #2e50b8 | #b7cdff | 84.1 | 75 |
fg-on-danger | #fffdfd | #fffdfd | 75.6 | 75 |
fg-on-warning | #fffdfb | #fffdfb | 75.2 | 75 |
border-strong | #a6a9b0 | #95989f | 46.3 | 45 |
Amounts are integer minor units in a bigint, ISO-4217 aware, rounded once and auditably. A cent that drifts is a dispute you lose.
Row-level security means a query that forgets whose rows it is reading returns nothing at all: enforced by the database, not by review.
A double-entry ledger under the whole thing: every charge, credit and refund is two entries that sum to zero, and you can prove it on demand.
Every kit runs on QuxCloud from the free tier up — or installs straight from npm. The open cores are Apache-2.0, billing-kit is source-available under BUSL-1.1, and either way the code is yours once you have it.
Every kit running on a workspace of your own. No card.
The whole family, with credits to build against.
The code in your repository, with SSO and a named contact.
Exact money down to the token, isolation the database enforces, auth that holds, and billing your agents can read — open at the core. The safe choice is also the faster one.