Multi-tenant SaaS
LoveHeartBeat isolates every organization on its own slug subdomain — built for thousands of tenants
Design target
30k+
URL model
slug
Plans
Trial → Ent
Isolation
org_id
Tenant URL model
Each organization gets a reserved slug that becomes its SaaS hostname:
https://<organization-slug>.loveheartbeat.com
——your organization
Apexloveheartbeat.comhandles marketing + login routing; subdomain resolves the tenant.
Isolation model
Designed so trial startups and large enterprises share one platform safely:
- Auth— Okta/SSO or native login per org
- Data— every query scoped by
org_id - Cloud / AI / ETL— connectors belong to the org
- Members— users invited into one or more orgs
- Limits— plan quotas (accounts, seats, AI spend)
Onboarding → production path
1
Create org + slug
Reserveslug.loveheartbeat.com
2
Auth mode
Okta/SSO or LoveHeartBeat passwords
3
Invite members
Roles under that org only
4
Connect sources
Multi-account AWS/GCP/Azure + AI + ETL
5
Observe
Dashboards, alerts, cost — tenant-scoped
Scale notes (~30,000 organizations)
Shared app, isolated data
One LoveHeartBeat deployment; tenant resolved from Host header (slug.loveheartbeat.com).
Stateless APIs
Lambda/API handlers always requireorg_idfrom subdomain + auth token claims.
Tiered tenancy
Trial/Business on shared pools; Enterprise can use dedicated queues, rate limits, and retention.
