Skip to main content
Learn how ArcKit helps architect scalable, multi-tenant platforms that serve multiple departments, teams, or customers whilst maintaining isolation and governance.

​
When to Use This Approach

Reference this guide when designing:
  • Multi-tenant SaaS platforms
  • Shared service platforms for government
  • Internal developer platforms (IDPs)
  • API gateways and integration hubs
  • Data platforms serving multiple teams
  • Centralized AI/ML platforms

​
Relevant Commands

# Initialise platform project
arckit init --type platform

# Platform architecture design
arckit.design --pattern platform

# Multi-tenancy and isolation design
arckit.tenancy

# API and integration documentation
arckit.integrations

# Cost allocation and chargeback
arckit.costs --model platform

# Security for multi-tenant systems
arckit.security --pattern multi-tenant

​
Example Walkthrough: UK Government Training Marketplace

Reference project: arckit-test-project-v10-training-marketplace This example demonstrates a multi-sided marketplace platform connecting government buyers with AI training providers.

​
Step 1: Platform Architecture

ArcKit documented the core platform services:
  • Tenant management and onboarding
  • Identity and access control
  • Marketplace transaction engine
  • Payment processing integration
  • Shared data services

​
Step 2: Tenancy Model

Generated isolation patterns for three tenant types:
  • Government buyers: Departmental accounts with procurement workflows
  • Training providers: Supplier onboarding and course catalogues
  • Platform operators: Administrative and monitoring capabilities

​
Step 3: Integration Architecture

Documented API gateway, webhooks, and integration patterns allowing tenants to:
  • Consume platform APIs
  • Receive event notifications
  • Integrate with departmental systems
  • Access shared reference data

​
Step 4: Cost and Chargeback

ArcKit produced cost allocation models:
  • Usage-based pricing per tenant
  • Resource quota enforcement
  • Chargeback reporting
  • Budget alerts and controls

​
Key Artifacts Generated

Platform Architecture

Core services, tenant boundaries, shared components

Tenancy Model

Isolation patterns, quota models, onboarding workflows

API Specifications

Platform APIs, webhooks, integration guides

Cost Models

Pricing, chargeback, quota enforcement

​
Platform Design Patterns

ArcKit documents multiple isolation models: namespace-based (Kubernetes), schema-based (database), and account-based (cloud). Choose based on security requirements and operational complexity.
Platform capabilities should be API-driven. ArcKit generates comprehensive API documentation, versioning strategies, and backward compatibility approaches.
Reduce operational burden with automated tenant provisioning. The design includes approval workflows, quota assignment, and welcome automation.
Monitoring, logging, and alerting must support per-tenant views. ArcKit captures tenant-aware telemetry, dashboards, and SLA tracking.
Platforms need cost transparency. Documentation includes usage metering, cost allocation tags, chargeback reports, and budget controls.

​
Best Practices

  • Start with Tenancy Model: Use arckit.tenancy early to establish isolation boundaries
  • Design for Failure: Document tenant-specific failure domains and blast radius containment
  • API Versioning: Plan API evolution strategy to avoid breaking tenant integrations
  • Quota Enforcement: Define resource limits per tenant to prevent noisy neighbour problems
  • Security Boundaries: Run arckit.security to verify tenant data cannot leak across boundaries

Cabinet Office GenAI Platform

Multi-tenant GenAI platform for government

ONS Data Platform

Data platform with Five Safes governance

UK Government API Aggregator

Unified API gateway for 240+ government APIs

Build docs developers (and LLMs) love

Get started for freeTalk to us