Tenant isolation
The architecture requires tenant-owned records to carry organization scope and encourages event scope where possible for safer filtering and policy design.
Security
Security and operational trust are built into the Eventberry architecture.
The product model depends on tenant isolation, audited access paths, signed preview controls, request correlation, and reliable background operations across public and admin surfaces.
Security pillars
The trust model depends on architecture, not a checklist page alone.
Eventberry ties routing, preview controls, auditability, and operational reliability together because those concerns overlap in real event systems.
Audited elevated access
Internal platform and support access is intended to use audited elevated pathways rather than informal bypasses.
Signed preview and public access controls
Draft public-event previews are protected through signed, short-lived preview access rather than being casually exposed on public routes.
Request and runtime visibility
Request IDs, runtime error intake, audit scaffolding, and job execution traces are part of the system foundation.
Controls
Controls span routing, auth, operations, and public-event delivery.
These sections describe how Eventberry is intended to behave across public launch, internal operators, and sensitive system actions.
Host-aware routing and surface separation
Apex marketing and tenant workspace traffic are separated by host-aware routing
Platform, support, and docs operate on dedicated internal hosts
Custom event domains resolve directly to launched public event experiences
Authentication and authorization foundations
Supabase SSR auth clients and session helpers back account access
Role bundles and function-level permissions define runtime authorization intent
Service-role work is isolated to worker or admin-only flows
Operational safeguards
Database-backed job execution is intended to be idempotent and retry-aware
Runtime errors and request correlation support operator investigation
Audit logging is part of the platform and tenant model for sensitive actions
Public-surface trust controls
Launch-state and archive-state rules gate what public routes can render
Preview cookies protect draft-event inspection workflows
Payments, email, and domain flows are designed to run through explicit provider integrations
Get started
Review the operating model together with the controls
The features, pricing, and legal pages explain how the product works. The security page explains how the architecture is intended to protect and support it.