Common signs: clients or institutions want their own instance, domain or data. Usual causes: a single shared deployment and manual setup for each client. What we do: build a repeatable template for per-customer instances. What you get: new customers deployed quickly and consistently.
Our per-customer deployment setup lets you give each client, college or institution its own copy of your app, with its own domain, database and settings, without setting each one up by hand. A Codersarts engineer turns your deployment into a template, so a new customer can go live quickly and every instance stays consistent and easy to update. Fixed price from $199 with 1-day delivery.
Per-Customer Deployment at a Glance
Item | Details |
|---|---|
Starting price | $199 for one extra instance |
Delivery | 1 day for one instance, 3 days for a reusable template |
Hosting | Hetzner, AWS, DigitalOcean, Google Cloud, Azure or the customer's own servers |
Per instance | Own domain or subdomain, database, settings and SSL |
Tools | Docker, Docker Compose, Terraform, Ansible or CI/CD pipelines |
What you get | A repeatable way to launch and update customer instances |
Revisions | One revision round included |
What Is Per-Customer Deployment?
Per-customer deployment, also called single-tenant deployment, means each customer gets a separate instance of your application with its own database and often its own server and domain. It gives strong data separation and lets customers have custom settings, which colleges, enterprises and regulated industries often require.
The challenge is operations: updating ten or fifty instances by hand doesn't scale. A template and automated deploys fix that.
Signs You Need Per-Customer Deployments
A college, enterprise or government client wants its own instance or domain
Customers require their data to be stored separately
Setting up each new client takes days of manual work
Instances drift apart because each was set up differently
Some customers want the app on their own servers
Why Per-Customer Setups Get Messy
Manual setup
Each instance is configured by hand from memory.
Hardcoded settings
Customer-specific values are written into the code.
No update process
Updating every instance is slow and error-prone.
No inventory
Nobody has a clear list of instances, versions and settings.
Quick Checks You Can Try First
Move customer-specific settings into environment variables or config files.
Make sure the app can run from a single Docker image.
Keep a list of every customer instance and its version.
Decide whether each customer needs a separate server or just a separate database.
If the problem remains, our engineers take it from there.
How We Set Up Per-Customer Deployments
Review. We check how the app is configured and deployed today.
Separate config. We move customer settings into configuration.
Build the template. We create a deploy template for server, database, domain and SSL.
Deploy. We launch the next customer instance from the template.
Update process. We set up a way to update all instances safely.
Document. We write a short guide for adding new customers.
What You Get
A deployment template for new customer instances
A new instance deployed with its own domain and database
Customer settings separated from code
A process to update all instances
An instance inventory and setup guide
Example result (illustrative)
A coding platform signed two colleges that each wanted their own domain and database. We moved college-specific settings into configuration, built a Docker and Terraform template on Hetzner, and deployed both colleges. A new college can now go live in under an hour.
What Is Included and Not Included
Included | Not included |
|---|---|
One extra instance or a reusable template | Rebuilding the app as multi-tenant |
Domain, SSL and database per instance | Server costs for each instance |
Update process for all instances | Managing customer-owned servers long term |
Setup guide | Custom features per customer |
Pricing for Per-Customer Deployment
Package | Best for | Starting at | Delivery |
|---|---|---|---|
One extra instance | Deploy the next customer from your current setup | $199 | 1 day |
Reusable template | Automated template and update process | $599 | 3 days |
Multi-tenant redesign | One shared app with isolated customer data | Custom quote | Agreed with you |
You get a fixed quote after we review your setup. You approve the scope before any payment.
Who This Is For
EdTech platforms selling to colleges and schools
B2B SaaS selling to enterprises
Platforms in regulated industries
Agencies running one product for many clients
What We Need From You
Repository access
How the app is deployed today
A list of customer-specific settings
Hosting account and domain access
Code and data privacy
We sign an NDA on request, work with the least access needed, and never keep copies of your data after delivery. You own all code, configuration and notes.
Key Terms Explained
Single-tenant: each customer has a separate instance
Multi-tenant: many customers share one instance with separated data
Infrastructure as code: describing servers and settings in files so they can be recreated automatically
Instance: one running copy of the app
Common Mistakes We Avoid
Copying the codebase for each customer
Hardcoding customer settings
Updating instances one by one by hand
Choosing single-tenant when multi-tenant would be cheaper to run
Need More Than One Task?
Deciding between single-tenant and multi-tenant? See Multi-Tenant Systems and Infrastructure as Code. Or use Prepaid Developer Hours to cover several tasks from one prepaid balance.
Related Tasks
Hetzner Server Setup for low-cost servers per customer
Backup & Restore Setup for each customer's data
Uptime Monitoring & Alerts Setup across all instances
Frequently Asked Questions
Should each customer have a separate instance?
Choose it when customers need strong data separation, their own domain or custom settings. Otherwise, multi-tenant is usually cheaper to run.
How do you update many instances?
With a single image and an automated deploy process that updates instances one by one, with rollback.
Can you deploy to a customer's own servers?
Yes, with a documented install and agreed responsibilities for uptime.
What does each instance cost to run?
It depends on size and host. On Hetzner, small instances can be very low cost per month.
Launch Every New Customer the Same Way
Share your app and how customers are set up today, and a Codersarts engineer will make new instances fast and repeatable.