Loading page
AI-native SaaS Launch OS
Private beta — see exactly what exists todayConnect the Paddle account you already have. Paycux keeps the catalog, plans, entitlements and usage limits, and hands checkout, portal and cancellation to your provider. It does not process payments or hold funds.
Built on the billing providers and infrastructure you already run
Available today
Everything below exists in the API and the console right now. It is the whole list — planned products are marked as planned wherever they appear on this site.
Developer-first design
No SDK to install. Your application calls a handful of JSON endpoints with the Keycloak token your user already holds; your team uses the console or the same API behind a session cookie.
JSON everywhere. Validation failures answer 400 INVALID_INPUT; every error has a named code.
Idempotency-Key on usage events and checkout sessions, so a retry never double-counts or double-sells.
Three identities that are never mixed: dashboard session, end-user realm token, provider webhook signature.
Provider API keys are verified with a read-only call, stored in OpenBao and leased per request — never returned or logged.
Projects and environments, each environment with its own Keycloak realm and its own provider connections.
Every catalog, membership and lifecycle write lands in the workspace audit ledger.
1# Record usage and get an allow/deny decision.2# Realm token = your application user's Keycloak access token.3curl --request POST "https://api.paycux.com/v1/usage/events" \4 --header "Authorization: Bearer <realm access token>" \5 --header "Idempotency-Key: 7f1c1e4a-usage-2026-09-03-0001" \6 --header "Content-Type: application/json" \7 --data '{8 "projectId": "<project id>",9 "environmentId": "<environment id>",10 "realmId": "<realm id>",11 "billingAccountId": "<billing account id>",12 "meterKey": "api_calls",13 "quantity": 1,14 "occurredAt": "2026-09-03T10:15:00.000Z"15 }'1617# 200 — UsageDecision18{19 "allowed": true,20 "reason": "WITHIN_LIMIT",21 "consumed": 1,22 "limit": 10000,23 "eventId": "<event id>",24 "duplicate": false25}
Catalog and entitlements
Define products, plans, prices, features and meters per environment. Map each plan to a price on your own provider connection. Archive what you stop selling — subscriptions that already exist keep working.
Illustrative keys and limits. Each plan maps to a price on your own provider connection; checkout sells the highest unarchived version.
Organisations and members
End users create organisations and invite colleagues through the API. Your team manages its own workspace — members, roles, invites, export and deletion — from the console.
End users create an organisation and become its owner
Invites are single-use tokens, stored only as a hash, expiring after 7 days
Acceptance requires the same verified e-mail — mismatches fail closed
Your team sees masked e-mails and can revoke a pending invite
Workspace owners and admins manage members; removing one revokes every session
Workspace export is secret-free JSON; deletion has a 30-day cancellation window
Where this is going
Seven of the product pages describe capabilities that exist today in part — per-environment customer identity, hosted sign-in screens, roles, organisations and invites, agent access, abuse damping and the audit ledger — and each page lists what is planned next to what works.
The remaining pages — hosted SSO, directory provisioning, customer secret storage, multi-factor policies and app connections — are planned and cannot be enabled.
Paycux is in private beta. Approved workspace plans and launch prices are published on the pricing page.
Create a workspace, connect a Paddle test key, define a plan, and send your first usage event.