■ The wallet model

Prepaid wallet. Predictable projects.

Your organization holds a USD wallet; every project draws from it with a monthly base plan plus metered overage — each service in its natural metric.

How billing works

Top up the wallet

Your organization's prepaid USD wallet funds everything — by card or local methods. A hard ceiling on exposure, no collection surprises.

Each project carries a base plan

Bundled quotas for requests, storage, and email — and the generated admin console included. Predictable enough to promise your client a monthly number.

Beyond quotas, natural metrics

WhatsApp per conversation, storage per GB plus egress, location per active device — never force-fitted to per-request.

The metrics table

Every service in its own unit.

Dollar amounts are announced at launch; the metrics are locked now — because the SDK and the metering engine emit them from the first release.

What	Metric	Note
Project base plan	Per project / month	Includes bundled request, storage, and email quotas; includes the generated admin console
API calls	Per 1,000 requests over quota	The uniform metric for standard services
File storage	GB-month + GB egress	Egress is metered separately — it is the real underlying cost
WhatsApp	Per conversation	Meta pass-through + margin
SMS	Per message	Provider pass-through + margin
Email	Per 1,000 over quota	—
Payments	% + fixed per successful transaction	Gateway fees passed through + platform fee
Real-time location / device streaming	Per active device / month	Never per request — a connected driver pings tens of thousands of times a day
PDF generation	Per 1,000 documents	—

Development never burns balance: sandbox is fully functional, moves no real money, sends no real messages.

Start in sandbox

Agency billing — two models, both formal flows

How the money flows is your call.

Model A — agency-owned

Recurring revenue

The project lives in your workspace; your wallet pays ProudBase. You resell consumption to your client with margin — recurring revenue on every delivered project.

Built for it: per-project cost attribution, client-ready invoices with your margin, spend caps.

Model B — client-owned

Direct billing

The project lives in your client's own account and their wallet pays directly. You typically stay on as a Collaborator — technical access without billing authority.

Built for it: invitation flow, zero-downtime ownership transfer — the same API keys keep working.

See the docs →

The zero-balance ladder — published policy

Your end clients' systems never just go dark.

A production system serving a restaurant or a clinic must not vanish because a wallet ran empty. The ladder is published policy — and export works at every stage.

1Warning

Balance below 25%, then 10%, of trailing 30-day burn

Alerts to the Owner — email, WhatsApp, in-app — repeated daily

2Grace

Balance reaches zero

72 hours of full service within a small negative-balance cap; urgent alerts

3Restricted

Grace expires

Reads, the admin console, and data export stay up; writes are refused with a clear, documented error code

4Suspended

7 further days

APIs off; data retained 60 days; export remains available throughout

5Deletion

After retention + final notice

Permanent removal under the data policy

Figures are published defaults, tuned before launch. Optional per-project spend caps stop one runaway project from draining the shared wallet.

Questions agencies actually ask

Do I need to pay to start?

No. Signing up creates your organization free of charge, and sandbox is fully functional without a wallet — it moves no real money and sends no real messages. You top up only when a project goes to production.

What happens at zero balance?

The published ladder above — never a surprise blackout: repeated warnings, then a 72-hour grace window at full service, then a restricted mode where reads, the admin console, and export stay up. Suspension comes only after all of that, and your data remains exportable throughout.

Can my client pay directly?

Yes — Model B. The project lives in your client's own account and wallet. Moving there is a formal invitation flow with a zero-downtime guarantee: the same API keys keep working, and you typically remain a Collaborator with full technical access.

Who owns the data?

You — or your client, depending on who owns the project. Full export from any service at any time, in open formats, including during restriction and suspension. No export ransom, ever.

Which SDK languages?

TypeScript now — one package, every service a typed namespace, generated from each service's OpenAPI spec so types and docs never drift. More generated SDKs follow once codegen makes them nearly free.

How do WhatsApp costs work?

Per conversation: Meta's pass-through cost plus our margin — priced in WhatsApp's own natural unit, not per API request. Templates, opt-ins, and two-way confirm/cancel flows are part of the product.

Open your organization.

Price your first project in an afternoon.

Create your organization