Home / Use cases / From single-tenant installs to one multi-tenant platform with a public API
SAAS & TECHNOLOGY
MID-SIZE
PLATFORM ENGINEERING
PUBLIC API
From single-tenant installs to one multi-tenant platform with a public API
Tenant isolation, automated releases and an API partners can build on. One multi-tenant platform with tenant isolation, a public API and automated releases.
Example engagement: figures show typical results for this kind of project.
1
platform, every customer on the latest version
11 mo
typical timeline
8
services working together
3
user roles, each with its own workspace
BUILT FOR
B2B SaaS companies running single-tenant installs
INDUSTRY
SaaS & Technology
TYPICAL SIZE
Scale-up
WHERE WE DELIVER
United States, Canada and Europe
TYPICAL TIMELINE
11 months
TEAM
Cross-practice: software, managed cloud, security, strategy
Services used:
Legacy modernization
API & integration
QA & DevOps
Web applications
Managed cloud
Cloud cost optimization
SOC 2 compliance
IT architecture assessment
IN SHORT
How do you move a SaaS product from single-tenant to multi-tenant safely?
In stages: design tenant isolation first, migrate customers in rings starting with internal and friendly tenants, and keep dedicated databases for customers who need them.
KEY TAKEAWAYS
→ Decide tenant isolation per data tier: shared, pooled or dedicated
→ Migrate customers in rings with rollback, never all at once
→ Release behind feature flags and canary by tenant ring
→ Treat your public API as a product with docs, keys and versioning
THE CHALLENGE
Sound familiar?
Strong product-market fit, but every new customer made the platform harder to run.
01
A separate copy of the product per customer
When each customer runs its own install, many fall behind on versions and every fix must be deployed again and again.
02
Releases took a month
Manual, per-customer deployments meant one release a month and weekend upgrade windows.
03
Enterprises wanted integration
Large customers and partners asked for a documented API, webhooks and SSO before signing.
TECHNICAL ARCHITECTURE
One platform, many tenants
Tenant context flows through every request, data is isolated per tier, and releases move through rings of tenants.
USERS & CLIENTS
Customer web app
Technician mobile app
iOS & Android
Developer portal
Partner integrations
API & webhooks
↓
EDGE & ACCESS
API gateway
Rate limits per tenant
Identity
SSO, SCIM, OAuth 2.0
Tenant router
Region and ring aware
↓
CORE SERVICES
Jobs & scheduling
Technicians & skills
Assets & parts
Billing
Notifications
↓
PLATFORM
Feature flags
Release rings
Canary by tenant ring
Event bus
Kafka
Webhook delivery
Signed, retried 72 h
↓
DATA
Pooled PostgreSQL
Row-level security
Dedicated databases
Enterprise tenants
Search index
Analytics warehouse
↓
INTEGRATIONS
ERP & accounting
CRM
IoT platforms
Parts suppliers
RELIABILITY & SECURITY
Across every layer
• Tenant isolation tested every release
• Dedicated databases for enterprise tenants
• SSO, SCIM and audit logs per tenant
• OAuth 2.0 for API clients
• Rate limits per tenant and per key
• Ring-based canary releases
• SOC 2 controls and evidence
• 24/7 monitoring and on-call
THE SOLUTION IN DETAIL
One platform, three types of users
Customers get new features faster, developers get a real API, and platform engineers run one system instead of many.
Product screens on this page show the design with sample data.
01
Customer teams
Customer workspace
6 core features
02
Developers & partners
Developer portal
6 core modules
03
Platform engineering
Tenant operations
6 core modules
01
CUSTOMER WORKSPACE
Customer teams
Dispatchers and managers schedule technicians, track jobs and measure service performance, now always on the latest version.
CORE FEATURES
✓
Dispatch board
Drag-and-drop scheduling by skills and distance.
✓
Smart assignment
Jobs auto-assigned to the best technician.
✓
Job detail
Asset, parts, SLA and live technician status.
✓
Customer portal
Customers raise and track jobs themselves.
✓
Service reports
First-time fix, SLA and productivity.
✓
Always up to date
New features every week, no upgrade windows.
F
Fieldbase
CUSTOMER WORKSPACE
Schedule
Jobs
Technicians
Customers
Reports
Dispatch board · Thursday 5 Nov
Northwest region · 64 technicians · 312 jobs
Search jobs, technicians, customers…
Technician
7:00
8:00
9:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
A. Moreno
HVAC service
Install
Repair
J. Smith
Boiler repair
Inspection
L. Chen
Callout
Install
Service
R. Okafor
Service
Repair
Inspection
S. Patel
Install
Service
Dispatch board
F
Fieldbase
CUSTOMER WORKSPACE
Schedule
Jobs
Technicians
Customers
Reports
Job #FB-204812 · Boiler repair
Customer: Harbor View Apartments · SLA: 4 hours · technician en route
Search jobs, technicians, customers…
Details
Asset
Boiler B2 · installed 2019
Issue
No hot water, error code E127
Parts
Pressure sensor (in van stock)
Assigned
J. Smith · ETA 11:20
Synced to
Customer ERP via Fieldbase API
Timeline
Created via customer portal
09:02
Auto-assigned (skills + distance)
09:03
Parts reserved
09:04
Technician en route
10:41
Job detail and timeline
F
Fieldbase
CUSTOMER WORKSPACE
Schedule
Jobs
Technicians
Customers
Reports
Service performance
Last 90 days · all regions
Search jobs, technicians, customers…
First-time fix rate
89%
+7 pts
SLA met
96.2%
Jobs per tech per day
4.9
+0.8
Customer rating
4.8 / 5
Jobs completed per week
Service performance reports
02
DEVELOPER PORTAL
Developers & partners
Customer IT teams and partners integrate through a documented, versioned API with webhooks, sandbox keys and a marketplace for finished integrations.
F
Fieldbase
DEVELOPER PORTAL
API reference
Keys
Webhooks
Marketplace
Usage
Fieldbase Public API v2
REST + webhooks · OpenAPI 3.1 · OAuth 2.0 client credentials
Search jobs, technicians, customers…
Endpoints
GET
/v2/jobs
POST
/v2/jobs
GET
/v2/jobs/{id}
PATCH
/v2/jobs/{id}
GET
/v2/technicians
GET
/v2/assets
POST
/v2/webhooks
POST /v2/jobs
curl -X POST https://api.fieldbase.io/v2/jobs \
-H "Authorization: Bearer $TOKEN" \
-d '{
"customer_id": "cus_8813",
"type": "repair",
"priority": "high",
"sla_hours": 4
}'
Rate limit: 600 requests/min per tenant · idempotency keys supported
Public API reference
F
Fieldbase
DEVELOPER PORTAL
API reference
Keys
Webhooks
Marketplace
Usage
Webhooks
Signed events with automatic retries for 72 hours
Search jobs, technicians, customers…
Recent deliveries
EVENT
ENDPOINT
RESPONSE
LATENCY
ATTEMPTS
TIME
200
184 ms
1
10:58:12
200
92 ms
1
10:57:40
503
—
3 (retrying)
10:55:03
200
61 ms
1
10:54:51
Webhook deliveries
F
Fieldbase
DEVELOPER PORTAL
API reference
Keys
Webhooks
Marketplace
Usage
Integration marketplace
38 integrations · 11 built by partners on the public API
Search jobs, technicians, customers…
ERP connector
Sync jobs and invoices
612 installs
Accounting
Invoices and payments
1,104 installs
CRM
Customers and contracts
498 installs
IoT monitoring
Create jobs from sensor alerts
221 installs
Parts suppliers
Live stock and ordering
304 installs
Payroll
Hours and overtime
389 installs
Integration marketplace
CORE MODULES
✓
OpenAPI reference
Every endpoint documented with examples.
✓
API keys & OAuth
Client credentials and scoped keys.
✓
Webhooks
Signed events with automatic retries.
✓
Sandbox
Test tenant with sample data.
✓
Marketplace
Integrations built by you and by partners.
✓
Usage analytics
Calls, errors and limits per key.
03
TENANT OPERATIONS
Platform engineering
Engineers run one platform across three regions, release in rings several times a day and see the cost of every tenant.
CORE MODULES
✓
Tenant registry
Every tenant with region, plan and data tier.
✓
Release rings
Internal, early adopters, 50%, everyone.
✓
Feature flags
Turn features on per tenant or plan.
✓
Health & SLOs
Latency and errors per tenant.
✓
Cost per tenant
Usage-based infrastructure allocation.
✓
Migration tooling
Single-tenant installs moved with validation.
F
Fieldbase
PLATFORM ENGINEERING
Tenants
Releases
Health
Cost
Tenants
1 multi-tenant platform · 3 regions · 1,240 customer tenants
Search jobs, technicians, customers…
Tenants
1,240
On latest version
100%
was 23%
Single-tenant instances left
0
was 120
Noisy-neighbour incidents
0
Largest tenants
TENANT
PLAN
REGION
USERS
API CALLS (24 H)
HEALTH
Harbor View Group
Enterprise · dedicated DB
US-East
2,410
1.8M
Healthy
Acme Facilities
Enterprise
EU-West
1,920
940k
Healthy
Northwind Services
Growth
US-West
610
212k
Healthy
Bluefin Utilities
Enterprise · dedicated DB
EU-West
3,050
2.4M
Healthy
Tenant operations
F
Fieldbase
PLATFORM ENGINEERING
Tenants
Releases
Health
Cost
Releases
Trunk-based development · feature flags · canary by tenant ring
Search jobs, technicians, customers…
Deploys per week
34
was 1 per month
Lead time for changes
1.2 days
Change failure rate
3.1%
Time to restore
18 min
Rings
Ring 0 · internal tenants
v2.48 live
Ring 1 · early adopters (5%)
v2.48 live
Ring 2 · 50% of tenants
Rolling out
Ring 3 · all tenants
Scheduled 16:00
Ring-based release pipeline
F
Fieldbase
PLATFORM ENGINEERING
Tenants
Releases
Health
Cost
Cost per tenant
Shared infrastructure with usage-based allocation
Search jobs, technicians, customers…
Infra cost per tenant
$42 / mo
−64%
Gross margin
81%
+12 pts
DB utilisation
71%
Idle environments
0
Infrastructure cost per tenant (USD / month)
Cost per tenant
TECHNOLOGY & SECURITY
A platform built to scale with every new customer
Modern, boring choices with tenant awareness everywhere.
TECHNOLOGY STACK
Frontend
React
TypeScript
React Native
Backend
Java 21
Spring Boot
Kafka
Data
PostgreSQL
Row-level security
OpenSearch
Platform
Kubernetes
Feature flags
Argo CD
API
OpenAPI 3.1
OAuth 2.0
API gateway
Cloud
AWS (3 regions)
Terraform
FinOps tagging
SECURITY & COMPLIANCE
✓ Tenant isolation tests in every pipeline
✓ Dedicated databases for regulated tenants
✓ SSO, SCIM and audit logs for every customer
✓ OAuth 2.0 scopes for every API client
✓ Per-tenant and per-key rate limiting
✓ SOC 2 controls maintained through the migration
✓ Zero-downtime, reversible tenant migrations
✓ 24/7 monitoring with SLOs per tier
DELIVERY TIMELINE
From many installs to one platform in about 11 months
Customers moved in rings, with rollback ready at every step.
Month 0
Month 1
Month 2
Month 3
Month 4
Month 5
Month 6
Month 7
Month 8
Month 9
Month 10
Month 11
Architecture assessment
Code, data, tenancy model, migration plan.
Wk 0–4
Multi-tenant foundations
Tenant context, isolation, data tiers.
Wk 3–14
CI/CD & release rings
Pipelines, feature flags, canaries.
Wk 6–16
Public API & developer portal
OpenAPI, OAuth, webhooks, sandbox.
Wk 12–28
Tenant migration rings 1–4
Internal, early, 50%, everyone.
Wk 16–44
Marketplace & partner program
Partner onboarding and listings.
Wk 30–42
Decommission & cost tuning
Old installs retired, FinOps.
Wk 42–48
Typical plan: about 11 months to one platform · tenants migrated in rings
One codebase to run, faster releases and a partner ecosystem on the API. One multi-tenant platform with tenant isolation, a public API and automated releases.
WHAT THIS USE CASE DELIVERS
Use case blueprint. Scope, timeline and team are confirmed in a written proposal for your project.
RELATED USE CASES
More work like this
SAAS
AI agents
SOC 2
Enterprise-ready AI agent with SOC 2 and ISO 42001 for AI startups
THE CHALLENGE
Enterprise legal teams like AI demos, then ask hard security and AI questions.
OUR APPROACH
An evaluation-gated AI agent, SOC 2 and ISO 42001 controls, and a self-serve trust center.
WHAT SUCCESS LOOKS LIKE
An AI product that answers security and AI reviews with evidence, not promises.
3
frameworks built in: SOC 2, ISO 42001, trust center
Read the story →
1 / 3
RELATED INDUSTRIES
Built for your industry
The industry behind this use case, and others where the same approach works.
All industries →
BLOG & RESOURCES
Insights for SaaS and technology leaders
Practical guides on compliance, AI features and scaling your platform.
View all resources →
ARCHITECTURE
Multi-tenant SaaS architecture that passes enterprise reviews
Silo, pool and bridge models and the isolation controls buyers check.
Akash Soni, Founder & CEO · 8 min read
MODERNIZATION
Legacy modernization, one module at a time
The strangler fig approach, without a risky rewrite.
Akash Soni, Founder & CEO · 8 min read
COMPLIANCE
SOC 2 for SaaS: unblock enterprise security reviews
The controls, reports and trust-center answers buyers check.
Akash Soni, Founder & CEO · 8 min read
FAQ
Multi-tenant SaaS and public API questions, answered
Short answers to what teams ask us most about this kind of project.
Still have a question?
Book a free consultation
What is multi-tenant architecture?
Multi-tenant architecture serves many customers from one shared application and infrastructure, while keeping each customer's data strictly isolated. It cuts hosting and maintenance costs compared with separate installs.
How long does it take to move from single-tenant to multi-tenant?
Moving from single-tenant installs to a multi-tenant platform typically takes 6 to 12 months, migrating customers in waves while both models run in parallel.
How do you keep tenants isolated?
We enforce tenant IDs at every layer with row-level security, scoped access tokens, encryption keys per tenant where needed, automated isolation tests and audit logs.
What is ring-based deployment?
Ring-based deployment releases changes to small groups of customers first, then wider rings after checks pass, limiting the impact of any problem and enabling fast rollback.
What makes a good public API?
A good public API has consistent design, clear versioning, strong authentication, rate limits, complete documentation with examples, SDKs and a sandbox for developers to test safely.
SERVICES IN THIS USE CASE
Legacy Modernization & Cloud Migration →
Modernize without a big-bang rewrite
API & Systems Integration →
Connect every system you run
QA, Testing & DevOps →
Ship faster with automated testing
Web Application Development →
Fast, secure web apps
Outgrowing your architecture? Let's talk.
Book a free 30-minute call. You'll leave with a first view of the right tenancy model and migration path, whether or not we work together.
The right tenancy model
A safe migration path
No obligation