Brandle Test Site

Core platform

The four primitives every product team needs on day one.

Authentication

Email, magic link, social, and passkeys. SSO and SCIM provisioning on team plans.

Billing

Subscriptions, metered usage, invoicing, and tax handling without writing a webhook.

File storage

Direct uploads with signed URLs, image transforms, and lifecycle rules built in.

Background jobs

A durable queue with retries, scheduled runs, and a dashboard that shows what is actually happening.

For teams scaling up

The four pillars that come into play once you have real customers and real revenue.

Analytics

Product events, funnels, and cohort retention without bolting on a separate analytics tool.

Transactional email

Templated sends with bounce handling and reply routing. Bring your own sending domain.

Feature flags

Targeting rules by user, plan, or arbitrary attribute. Roll out gradually and roll back instantly.

Audit trail

Every state change, every actor, every timestamp. Exportable on demand for compliance reviews.

How it fits into your stack

Common integration questions, answered the way engineers want them answered.

Can I run it next to my existing backend?

Yes. Brandle Test Site is designed to sit alongside your application code. Most teams call our APIs from their server, mount our embeddable widgets on the client, and treat us as a managed service for the boring plumbing.

What languages and frameworks are supported?

Official SDKs for TypeScript, Python, Ruby, Go, PHP, Java, and Rust. The REST API is plain JSON, so anything that speaks HTTP can talk to us.

How does data import work?

Bring users, subscriptions, and historical events through a single CSV upload or a streaming import endpoint. Idempotency keys make repeated imports safe to retry.

What does the local development loop look like?

A CLI spins up a sandbox environment in seconds with seeded test data. Webhooks tunnel into your laptop so you can iterate without a public URL.

How do you handle environments?

Separate sandbox, staging, and production environments, each with their own API keys and isolated data. Promotions between environments are one command.

What happens during an outage on your end?

Reads continue from a cached snapshot. Writes are queued and replayed when the primary recovers. We publish a transparent post mortem within seventy two hours of any incident.

Everything your product needs