Teamli
Teamli | Beta Security
Security Overview

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.

AES-256
Encrypted at rest
FORCE RLS
Tenant isolation in the database
~870
Automated tests each release
EU
Hosted in europe-west1, CMEK
Last updated: July 7, 2026

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.

Browser

React SPA

Firebase Hosting (static + CDN), served over HTTPS.

→
API

Express API

Google Cloud Run. Verifies identity and enforces roles on every route.

→
Data

PostgreSQL

Google Cloud SQL with row-level security, encrypted at rest (AES-256).

Firebase Authentication · identity Cloud Storage · documents & photos Secret Manager · keys AI assistant · no training on your data

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

In transit HTTPS / TLS on every connection: browser to API, API to database.
At rest AES-256 across the entire Cloud SQL database and Cloud Storage files (customer-managed keys on request).
Access Row-level security + role permissions gate compensation, and it is never returned by the external API.

Core security controls

Identity and authentication

Sign-in is handled through Firebase Authentication with per-organization support for Google, Microsoft, and email/password. Platform administrators use explicit elevated claims.

Tenant isolation

Multi-tenant isolation is enforced at the database layer using PostgreSQL row-level security, with API requests executed inside tenant-scoped database context.

Role-based access control

Access is enforced by role and route, with separate behavior for employees, managers, admins, and platform super admins.

Document and data protection

Documents are served through signed URLs, production CORS is restricted to owned origins, and sensitive fields are filtered based on access level.

Auditability

Sensitive actions such as employee changes, tenant administration, document workflows, and lifecycle actions are written to audit logs.

Stability controls

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.

We don't ask you to trust a slogan. We'll show you the controls, the auditability, the isolation model, and the operating discipline behind the product.

Security review contact

For pilots and security reviews

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

Recommended next read

The customer-facing FAQ is available at /security/ and answers the most common pilot-stage security questions directly.