Built on multi-tenant isolation.
Every resource is scoped to an organisation, with HMAC-signed session cookies and service-role DB access so there's no cross-tenant leakage.
Overview
Postwyse is multi-tenant by design. Every row carries an org_id, every API route checks the session's organisation, and the database is accessed via a service-role key with application-level authorisation.
HMAC-signed session cookies, bcrypt-hashed passwords, and an audit log over key actions.
What you can do
Multi-tenant row scoping
HMAC-signed session cookies
bcrypt password hashing
Audit log over sensitive actions
How it works
Create an organization, invite your team and connect your domains and social accounts once.
Bring your own AI keys, set rate limits, rotate credentials and lock down sensitive exports.
Multi-tenant isolation, audit logs and SSO keep you compliant as your footprint grows.
Who it's for
Least-privilege service keys, audit trails and SSO — ready for a security review.
Separate orgs per brand with isolated data, billing and AI usage.
Dedicated environments, custom DPAs and a named CSM on Enterprise plans.
Frequently asked
Every record is scoped by org_id and enforced in application code with least-privilege service keys.
Claude (Anthropic) and Grok (xAI) ship out of the box. OpenAI and Perplexity are supported for research.
Managed cloud today. A single-tenant deployment option is available on Enterprise.
SOC 2 Type II readiness, GDPR and CCPA support. DPAs are available on request.
Works well with