--- title: "Multi-tenant SaaS development, from prototype to production · Volcanic Minds" description: "We develop custom multi-tenant SaaS platforms: data isolated per client, subscriptions with Stripe, cloud and DevOps. The source code stays yours." url: "https://volcanicminds.com/en/saas-development" lang: "en" type: "first_level_page" updated: "2026-10-12" alternate: "https://volcanicminds.com/saas-development" summary: "We build SaaS platforms from prototype to production: one installation that serves all your clients while keeping their data separate, with plans, recurring payments and licenses that each client manages on its own. We follow the whole cycle, from analysis to cloud infrastructure and releases, and the code stays yours: there is no license fee on the software we develop." --- # Multi-tenant SaaS platform development From prototype to subscription platform, with each client's data kept separate and the code owned by you. ## A SaaS is a product, not a management system with a login Software becomes a SaaS when the same installation serves many clients, and each of them uses it as if it were theirs alone. That calls for choices made at the start: how the data and configuration of different companies are kept apart, how a new client signs up and pays without going through you, how a new version ships without stopping the people at work. Postponing them is expensive. A platform born for one client and then copied for every new contract holds up while the clients are few; after that, every fix has to be repeated on every copy. That is why we design multi-tenant from day one: a new client is a configuration, not one more installation. ## The building blocks every SaaS needs. *What it covers* ### Data isolated per client Each organization has its own workspace, with data, users, configuration and contacts independent from those of the other clients. ### Plans and recurring payments Different plans, automatic renewal and payments by card or direct debit through Stripe. The client changes plan on its own, without writing to you. ### Self-service sign-up and licenses A new company registers, picks its plan and manages its licenses from its profile. Your team looks after clients, not activations. ### Invoices and tax rules Billing follows the rules of whoever pays. In a healthcare platform the backend recognizes the tax regime of each professional and talks to Fatture in Cloud. ### Access and roles Multi-factor authentication and role-based permissions, so each user sees only the data that is theirs, inside their company and across companies. ### API-first integrations Every function goes through an API, so the platform connects to your clients' management systems and their systems can connect to it. ## Growing without a rewrite *Cloud architecture* The platforms we build run in containers: resources grow with requests and users, and heavy operations sit on dedicated services, so they do not slow down the rest. Costs and performance stay adjustable, because capacity follows real use instead of being bought in advance for the worst case. We are not tied to one cloud provider: the list of those we work with is in the answer on [where the data lives](/frequently-asked-questions#hosting-e-residenza-dati). European cloud, sovereign cloud, your own account or an installation at a client that demands it: the choice is made at the start, on the regulatory, contractual and budget constraints of your product. ## Releases that do not stop your clients *DevOps* In a SaaS, releases do not end at go-live: they arrive while clients are working. That is why we design and write the infrastructure together with the software, as in the resource and project planning platform, where DevOps infrastructure and container deployment were part of the project. Access to infrastructure, backups and pipelines stays yours: you can review or revoke it without going through us. After go-live two numbers matter: how often the data is saved and how quickly the service restarts if something stops. RTO and RPO have no standard value; we set them with you, based on what an hour of downtime costs you. Maintenance, if you entrust it to us, is a separate contract with explicit SLAs. ## From the prototype to a subscription product. *The path* 1. **Business model analysis** — Before the code, we decide who the platform's clients are, what they buy and how they pay. Plans, limits and billing are product choices that become architecture. 2. **Prototype** — An idea is validated with a prototype before investing in full development. In the auditing platform with AI agents, the first working MVP arrived within six to eight weeks. 3. **Milestone development** — We release in increments, at the end of sprints, starting from what is worth most to the first clients. Real use decides the next priorities. 4. **Go-live and evolution** — Tests with selected users, a full check of the system and a handover with documentation. Then the product keeps growing with new versions. ## Where we have already done it. *Case studies* ### Advanced agentic AI auditing platform Multi-tenant, with an isolated workspace for each organization. Developed end to end, from analysis to infrastructure, in about four months. ### ESG platform for the supply chain Subscriptions with different plans, recurring payments by card or direct debit via Stripe, and licenses each company manages on its own. ### Bookings and healthcare assistance Split payment with Stripe, Fatture in Cloud and different tax regimes, on an infrastructure designed to orchestrate more than 30,000 services. ### Mechanical workshop management A containerized SaaS, built API-first, that grows with requests and with the team using it. ### Resource and project planning A multi-company system with multi-factor authentication, role-based permissions and DevOps infrastructure written together with the software. ### Data intelligence for prediction markets A SaaS platform that aggregates on-chain and market data, with subscription access. - [All case studies](/case-studies) - [Read the deep dive on multi-tenancy](/insights/multi-tenant-ai-saas-strategy) ## What we are asked before building a SaaS. *Frequently asked questions* ### How long does it take to reach production? It depends on how many domain rules the product carries, but there is an order of magnitude. The multi-tenant auditing platform was developed end to end, analysis and infrastructure included, in about four months, with a first working MVP within six to eight weeks. The real estimate comes out of the analysis. ### Multi-tenant, or one installation per client? One installation per client costs less to design and much more to keep up to date, because every fix has to be repeated on every copy. Multi-tenancy asks for more work at the start and pays back as the clients grow. If a client demands an environment of its own, a dedicated installation on the same codebase can be considered. ### Is the platform's code ours? Yes, 100%, and we write it into the contract. There is no license fee and no vendor lock-in on the software we develop, so you sell the product without asking us for permission. ### Which payment systems do you integrate? In the published projects, Stripe for cards, direct debit and split payment, and Fatture in Cloud for invoicing. If your market asks for something else, the integration is designed during analysis like any other. ## Tell us about the product you want to sell. Clients, plans and rules: we start from there to work out what to build now and what can wait. - [Let's talk about your project](/en/contacts)