Vorchestra: SaaS tenant orchestration platform

Running a SaaS where every tenant gets an isolated environment means a lot of repetitive server work: provision, deploy, configure, update. Done by hand it's slow and error-prone.

• Split responsibilities across focused .NET services: a core orchestrator (tenants, servers, plans, projects), a script registry with variable substitution, an SSH execution engine, and trigger-based workflows.
• Used CQRS with MediatR per service and a database-per-service data model.
• Wired services together with MassTransit and RabbitMQ so deployments react to events: a new subscription or a code update kicks off the right workflow.
• Ran actual deployment steps as versioned bash scripts executed over SSH, with tenant/server/project variables resolved centrally.

• Tenant lifecycle, from subscription to a running isolated environment, is driven by events instead of manual steps.
• Deployment logic lives in one script registry rather than scattered across servers.

• Backend on GitHub ↗
• Frontend on GitHub ↗