■ The one-page security overview
Why build your product on us? The answer lives in the product.
The first objection every serious agency raises is the right one. This page is the standing answer — printable, for your buying committee.
Data ownership
Your data is yours, always.
Export — anytime, in any state
- Full export from any service at any time, in open formats (CSV/JSON)
- Export remains available during restriction and suspension
- Published retention windows — 60 days post-suspension before any deletion
- No export ransom, ever — export is never priced
Operational transparency
- Public status page — status.proudbase.com
- Published SLA targets and honest incident communication
- Documented API versioning and deprecation policy
- The zero-balance ladder is published policy, not fine print
Security baseline
- RBAC and audit trails on sensitive actions
- 2FA on platform accounts
- Encryption in transit and at rest
- Per-project isolation; per-project quotas and rate limits
- Tested backups
Skin in the game
- ProudBase's own billing, invoicing, and operations run on the same catalog services customers buy
- We feel our own outages first — dogfooding is our earliest alarm
- Every catalog service has at least one demanding production user: us
ProudBase runs as microservices on AWS behind a single API gateway; every request carries project and subscription context, enforced before any service logic runs. Questions for your security review: [email protected]
Ready when your committee is.
Print this page for the meeting — then start in sandbox for free.