DevQux
Engineering arm of QuxKitWe build the software the kits are for.
Build it with the team that built the family.
Implementation, migrations, custom kits and adapters, and review. Your repository, your database, and a handoff that leaves your team able to run it.
Software we have already shipped.
Not slides: six applications running today, each built on the kits and each with a page of its own. This is the same team, on your product.
What you
can build
A product that is finished on day one
App-Kit is a new application that already has accounts, teams, billing and a design system wired together, on one database and one domain the product, the API and an agent all read.
app-kit
identity-kit
tenant-kitSomething you can bill by the token
billing-kit meters events, prices them to a fraction of a cent, and records every movement in a double-entry ledger, on a Money type a floating-point error cannot touch.
billing-kitAn assistant that answers from your own corpus
rag-kit plans a question into parallel waves of workers, each with recall over your documents and allowlisted tools, and merges what they find. Bounded and durable on your Postgres.
rag-kitA back office wired to what you already run
integration-kit reaches external systems through one small contract, each integration a versioned definition in the database; mail-kit and the conversations engine carry what has to be said to a customer.
integration-kit
mail-kitHow an
engagement
starts
Implementation
Billing, tenancy, identity and mail fitted to the app you already run, composed on one database so the kits reinforce each other instead of colliding.
Migrations
Off billing glued together by hand, a home-grown multi-tenancy or an auth you have outgrown, without a big-bang cutover or a data-loss weekend.
Custom kits and adapters
A payment provider, an SSO or SCIM bridge, a bespoke metering model: built against the same typed contracts the shipped adapters use.
Architecture review
A read of your money math, tenant isolation and auth posture, with a written account of what is safe, what will bite, and the order to fix it in.
Scoped to an outcome
Every engagement is shaped around something shipped and verifiable, with the price agreed before it starts.
In your repository
We work on your code and your database. Nothing depends on us at runtime once we leave.
Straight about fit
If the open kits or QuxCloud already cover you, we say so rather than sell an engagement you do not need.
Tell us what
you are building.
A short note about your product and where it hurts is enough to scope a first conversation. If design is the part that is missing instead, that is DesignQux.