SaaS application development and multi-tenant platforms
Have an idea for software you'd sell to other businesses as a monthly subscription? Or an internal tool that works so well others would pay for it? We help turn it into a SaaS product.
SaaS is software users don't install, but access through the browser and pay for as a subscription. In most SaaS products, all customers use the same application and each one sees only its own data. That's called a multi-tenant architecture.
For you, it means one application to maintain and update instead of a separate copy for every customer. A new feature reaches everyone on the same day, and the tenth customer doesn't take ten times more work than the first.
01
How we separate customer data
This is the most important decision in a SaaS project, and it's made at the start because it's hard to change later. All customers' data can live in one database with every record tagged with its owner, in the same database but in a separate schema per customer, or every customer can have its own database.
One database is simpler and cheaper to maintain when you have many smaller customers. Separate databases make sense when you work with large enterprises, sensitive data or customers who require their data to be physically separated. Sometimes both are combined.
Whichever way you decide, we verify the separation with automated tests. A user from one company must never see another company's data - not by mistake, and not through some forgotten report.
02
What every SaaS product needs
company sign-up and inviting colleagues to the account
roles and permissions within each company
subscriptions, free trials and billing through a payment provider
per-customer settings, from logo and colors to a custom domain
an admin panel for you, showing all customers, subscriptions and usage
an audit log of who changed what and when
This isn't what customers will remember your product for, but without it the product can't be sold. That's why we build it as a solid foundation, so most of the time goes into what makes your product different.
03
First version, then growth
The most expensive mistake in SaaS is a year of development before the first customer tries it. That's why we suggest a first version with the smallest set of features someone will pay for, and talking to the first users as early as possible.
Even so, we build the architecture to handle growth from day one. When your hundredth customer arrives, you shouldn't need a new application, only more infrastructure. Everything else about how we build custom applications is on our web application development page.
For example, our own Profile Amplify is a SaaS platform for restaurant chains that brings together reviews from five sources: Google Business Profile, Tripadvisor, Yandex, Google Play and the App Store.
FAQ
Questions about SaaS development
It's a way for one application to serve many customers while each one's data stays separate. Everyone uses the same code, so you maintain one application instead of dozens of copies.
It depends on the number of customers, the type of data and your customers' requirements. We explain the benefits and costs of both approaches before development starts.
Yes. A customer can use the application on its own domain with its own branding, while underneath it's the same application everyone else uses.
We define that in the contract before development starts, based on how you plan to develop and sell the product.
Often, yes. The biggest job is usually separating data by customer and adding subscriptions, so we first review the code and estimate how much of it can stay.