Twisted Mountain Animation / Tenant provisioning

Automating tenant onboarding

I automated the setup needed to make a new tenant available across multiple services at Twisted Mountain Animation.

Senior Software Engineer Nov 2025–Present

Tenant onboarding time~1 hour→ <2 minutes*Measured on multi-service tenant provisioning workflows at Twisted Mountain Animation (2025–2026).

The problem: Why does manual multi-tenant onboarding create enterprise bottlenecks?

Onboarding an enterprise SaaS tenant requires creating isolated database schemas, provisioning access credentials, and registering configurations across multiple distributed microservices. At Twisted Mountain Animation, engineers manually executed deployment scripts and database configurations for each new studio, consuming ~1 hour per tenant, causing customer onboarding delays and human configuration errors.

What I built: Automated provisioning and event-driven tenant activation

  1. How do you automate multi-service tenant database provisioning?

    Automated tenant provisioning orchestrates schema migrations and database namespace creation across multiple distributed microservices simultaneously using scripted infrastructure hooks. By eliminating manual database configuration steps at Twisted Mountain Animation, this automated pipeline compressed new client workspace initialization time from approximately 1 hour down to under 2 minutes.

  2. How does centralized secret management protect isolated tenant credentials?

    Isolating tenant credentials requires dynamic, scoped secret generation managed through HashiCorp Vault. Each tenant environment receives unique, least-privilege database credentials and access keys injected at runtime via environment leases, preventing credential leakage across multi-tenant boundaries without storing hardcoded static secrets in service repositories.

  3. How does event-driven activation enable zero-restart tenant onboarding?

    Publishing tenant creation events over Redis Pub/Sub notifies all running microservices of the new tenant configuration instantly. Services update their in-memory tenant routing tables dynamically without needing service restarts or rolling deployments, ensuring zero downtime and immediate availability for newly provisioned enterprise client workspaces.

The result: How did automated provisioning cut SaaS tenant onboarding from 1 hour to <2 minutes?

By combining declarative database provisioning scripts, HashiCorp Vault secret leasing, and Redis Pub/Sub event-driven cache invalidation, tenant onboarding time dropped from 1 hour to under 2 minutes. The system eliminated manual DevOps intervention, isolated tenant security, and enabled immediate self-service enterprise workspace activation.

*Internal production infrastructure benchmark. Actual setup duration depends on service count and database schema size.