The account everything else hangs off.
QuxCloud began as hosted billing-kit and turned into the hub. It is where the metering runs, where seats and entitlements live, where the applications are reached, and where the documentation is kept. One account, one invoice, one place to look — for a family of libraries that otherwise deliberately share nothing but an interface.
Hosting for the parts that want operating.
Most of the family is libraries: you install them, they run on your database, and we never see them. Some things genuinely want a host — a meter that must not lose an event, a licence that must be checkable, a reference that must stay current. That is what this is, and deliberately not more.
Metering and billing we operate
The billing-kit engine, run as a service: usage in, exact money out, settled through the provider you already use. Idempotent by construction, so retries and replays converge instead of double-billing. It is the same library you could self-host — the difference is who carries the pager.
One account, every entitlement
Seats, licences and plan state for the whole family live here. A seat token minted for one developer unlocks the commercial engines they hold, and nothing else. There is no second place to look and no second invoice to reconcile.
The documentation
Guides and API reference for every kit, behind your account rather than the open web. The libraries themselves stay exactly as licensed — what a QuxCloud account buys is the reference, kept current with what actually shipped.
The applications, joined up
QuxMail, QuxKit CRM and AI Member Cloud each run on their own domain, and each recognises this account. Sign in once; the dashboard is where they are reached, provisioned and paid for.
Priced by what you meter
Two published amounts — $49 and $299 a month — plus a per-event rate billed to the cent and never rounded per event. The rate card is on the pricing page, not behind a call, because a usage platform that hides its price is asking to be trusted twice.
Your data stays yours
Nothing here is a lock-in surface. The engines are libraries you can run on your own Postgres tomorrow, the schema is yours, and leaving means running the same code somewhere else rather than exporting to a competitor.
Where the name went. This was “billing-kit Cloud” while billing was the only thing it hosted. It now carries the seats for UI-Kit, rag-kit and the rest, the entitlements for the component libraries, and the documentation for everything — so it is named for what it became. The plans are unchanged, and so is every subscription on them.
One account, the whole family.
Start on the published rate, keep the libraries you already run, and get the seats, the applications and the documentation in one place.