Solutions

Yours to install, and keep

Some of the family is software you run. This is the other half: a scaffold, an agent crew, an integration engine and a design layer. All of them built to install into your own repository and stay there. No runtime to operate, nothing phoning home, no version we can take away. See all four working first on QuxCloud, against a tenant of your own, and take the code into your repo when you are ready. Looking for the finished applications instead? Those live under Applications.

See them running on QuxCloud See the kits underneath
npx create-quxkit-app my-app
The scaffold · Commercial

App-Kit

Start on day two hundred. One command gives you a new app that already has accounts, teams, billing and a design system fitted together — and a domain your product, your API and an AI agent all read from one place.

Explore App-Kit
one questionanalystresearcherauditorone cited answer
The agent crew · per seat

RAG-Kit

Retrieval-augmented generation usually means one model, one loop, and hope. This is the other shape: a planner decomposes the request, workers run in parallel waves with recall over your own corpus and tools they are allowed to use, and a synthesizer merges what they found — plans validated, tools allowlisted, every budget enforced.

Explore RAG-Kit
execute("salesforce", "message.send")
The integration engine · embed it

Integration-Kit

Connect any external system through one small contract. Every integration is a certified, versioned definition in Postgres — built once, served to every tenant — and your product never learns what Salesforce is.

Explore Integration-Kit
npx @quxkit/ui-kit-cli init --brand "#44403D"
The family’s design layer

UI-Kit

A design system that is generated, not assembled. One brand colour in. A contrast-verified theme in both modes, fifty components speaking one vocabulary, and the machine-readable contracts a coding agent needs, out. The ramp below it is what the engine makes of the stone in its own mark.

Explore UI-Kit

How to get these today. Start on QuxCloud. All four run there against a tenant of your own, with nothing to install and nothing to stand up first. Then take the code: the core kits are on the public npm registry — Apache-2.0, with billing-kit source-available under BUSL-1.1 — and for the rest of the family the way in is to talk to us. The cores stay open, and yours to keep once you have them. That has not changed, only the door has. The kits underneath are the same story, and more solutions are on the way as the family grows.