How Teamli handles security in beta.
This overview is intended for prospective beta customers who want a direct summary of current architecture, access controls, auditability, and the operational posture behind the product.
Current production architecture
One EU region (europe-west1), all Google Cloud managed services. Every request authenticates and is placed into a tenant-scoped database context before any data is read. The front-end holds no customer data.
React SPA
Firebase Hosting (static + CDN), served over HTTPS.
Express API
Google Cloud Run. Verifies identity and enforces roles on every route.
PostgreSQL
Google Cloud SQL with row-level security, encrypted at rest (AES-256).
The security-critical controls live in the platform, not our app code, so the guarantees hold even if our application has a bug.
How data is encrypted
Core security controls
Sign-in is handled through Firebase Authentication with per-organization support for Google, Microsoft, and email/password. Platform administrators use explicit elevated claims.
Multi-tenant isolation is enforced at the database layer using PostgreSQL row-level security, with API requests executed inside tenant-scoped database context.
Access is enforced by role and route, with separate behavior for employees, managers, admins, and platform super admins.
Documents are served through signed URLs, production CORS is restricted to owned origins, and sensitive fields are filtered based on access level.
Sensitive actions such as employee changes, tenant administration, document workflows, and lifecycle actions are written to audit logs.
The API uses rate limits, query timeouts, error sanitization, and deliberate destructive action flows to reduce operational risk.
Beta transparency
Teamli is in beta. The security foundation is in place, while the broader trust package is still maturing. We won't claim there is no risk. We will show you the controls we have, how we operate them, and what we're still hardening.
- Strong today: tenant isolation, authentication, role-based access, audit logging, and guarded destructive actions.
- Still maturing: broader compliance packaging, security-questionnaire packs, and deeper document governance.
- How you can review: an architecture walkthrough, an access-model review, and a look at our beta hardening roadmap.
Security review contact
Contact your Teamli beta point of contact to request an architecture walkthrough, security questionnaire support, or a review of current controls and remaining beta hardening work.
Direct contact: security@teamli.co
The customer-facing FAQ is available at /security/ and answers the most common pilot-stage security questions directly.