Loading page
Grow faster. Go further.
Paycux is a billing and entitlement control plane for software companies that run their own Stripe or Paddle account. Start in private beta with what is implemented today; the identity products on this page are planned and labelled as such.
Paycux is onboarding its first group of teams. There are no customer logos on this page yet — when there are, they will be real.
See who it is built forThe stack
Every product below is planned and none can be enabled today. Each is labelled on its own page; what exists now is the billing and entitlement control plane listed under What exists today.
Why Paycux for Startups
Small teams do not have a spare quarter for identity plumbing. Every decision below exists to keep that quarter yours.
The planned identity products are designed to work standalone, so you would pick what a deal actually requires. Today the billing and entitlement control plane is the product; the rest is roadmap.
The implemented control plane is a JSON API with three documented credentials. There is no SDK in any language today; the docs show curl calls, not install commands.
Paycux models organisations and workspace membership in the control plane, removing the users-to-teams relationship from your billing and entitlement layer.
Workspace plans and their prices are published on the pricing page. Nothing is billed during private beta, and no charge starts until you complete checkout.
The implemented routes and their credentials are published verbatim from the release source. Build against a non-production environment you own, with the team on hand while you do it.
Integrate against the contract
There is no Paycux client library today. The control plane is JSON over HTTPS; this example records a usage event with your application user’s credential and gets an allow or deny decision back. Point it at a non-production environment, ship when the checks pass.
1curl -X POST https://api.paycux.com/v1/usage/events \2 -H "Authorization: Bearer $REALM_ACCESS_TOKEN" \3 -H "Idempotency-Key: usage-2026-10-13-000001" \4 -H "Content-Type: application/json" \5 -d '{6 "projectId": "<project uuid>",7 "environmentId": "<environment uuid>",8 "realmId": "<realm uuid>",9 "billingAccountId": "<billing account uuid>",10 "meterKey": "api_calls",11 "quantity": 1,12 "occurredAt": "2026-10-13T09:00:00Z"13 }'1415# 200 { "allowed": true, "reason": "WITHIN_LIMIT", "consumed": 1, "limit": 1000, ... }
Early access
Tell us what you are building and where enterprise requirements are blocking you. We take on a small number of teams at a time so onboarding stays hands-on.
What you sell, who buys it, and which identity requirements have shown up in a deal so far.
A short call to work out which products you need on day one and which can wait for the next customer.
Integrate against a non-production environment of your own project, with direct access to the team while you do it.
Apply with a couple of sentences about your product. If Paycux is not the right fit yet, we will say so rather than sell you a plan.