A SaaS product from scratch
The application, per-organisation administration, subscriptions and the end customer’s portal. With isolated data from the first line of code, not bolted on later.
SaaS platforms we build and operate ourselves
A SaaS platform is not an application on a server with several accounts. It is an application where each organisation sees strictly its own data, with its own settings, subscription and permissions — while you, the provider, administer everything from one place and pay for one infrastructure.
We run three such platforms in production, built on the same core: AutoGarage for car workshops, RSVTIst for ISCIR operators and Pirueta for dance schools. The shared modules — authentication, subscriptions, invoicing, notifications, customer portal, mobile app — are already written, so a new vertical does not start from zero.
- Multi-tenant
- Keycloak
- Elasticsearch
- Spring Boot
- Angular
- Stripe
01
What we build
From a whole product down to the one module missing from a platform that already exists.
A new vertical on our core
If the niche resembles one we already cover, we start from the existing modules and build only the specific part. Production in weeks, not months.
Subscriptions and billing
Plans, trials, recurring invoicing and the link to the invoicing provider. Payments through Stripe, with subscription status visible inside the app.
A portal for your customer’s customer
The page the end customer sees: order status, their documents, appointments, payments. Through a tokenised link or an account, as needed.
Mobile app
For the people working in the field: the same data, role-based permissions, usable on a bad connection. Android and iOS from one codebase.
Moving off the old system
Import from a spreadsheet, an old database or another program, with mismatched rows checked before the import rather than after.
02
What you get
Data isolated per organisation
Each organisation has its own index; a query cannot return another one’s data, not by accident and not through a forgotten filter.
One codebase, many organisations
A fix is made once and reaches every customer. No per-customer branches that become impossible to maintain.
Predictable running costs
The infrastructure is sized for everyone, not for each. You know from the start what a new customer costs you per month.
Operation included
Monitoring, alerts, updates and interventions. We operate our own platforms, so we are not handing you something we would not keep running ourselves.
03
How it runs
Three stages, each ending with something usable.
- 01
Product analysis
Who the organisations are, what they pay for, what their customers see and what happens with the first real customer. The modules come from there, not from a feature list.
- 02
Core and first customer
We build the application and put it to work with a single real customer. The flow is checked with real data before it opens to everyone else.
- 03
Opening up and operating
Subscriptions, self-service signup, portal, mobile app. We stay on monitoring and on the changes customers ask for.
Questions about this service
What does multi-tenant mean in practice?
It means one application serves several organisations, each with completely separate data. In our platforms every organisation gets its own data index; the application cannot reach another organisation’s data even if someone forgets a filter, because the isolation sits below the application code.
How long until the first paying customer?
For a vertical built on our core, the first modules go into use in 6–8 weeks and subscriptions can open alongside them. A brand-new product in a different niche starts with an analysis stage and a pilot customer.
Can you take over an existing platform?
Yes, and we do it often: we read the code, write down what we found and propose a plan — what gets fixed, what gets rewritten and what stays. A takeover starts with a period where the system simply runs under our hands, unchanged, so we learn it before touching it.
Who operates the platform after launch?
We do, if you want. We run our own platforms on the same infrastructure with the same alerts, so it is not a service invented for the contract. If you prefer to operate it in-house, we hand over infrastructure described in code, not in a document.
Who owns the code?
The code and accounts of the work stay with the client at the end of the project. The modules from our shared core remain ours and are used under licence — which is also why a new vertical costs less than a platform written entirely from scratch.
Contact
Have a niche and no software for it?
Tell us how people in that niche work today. If it resembles something we already have, we will tell you in the first conversation what comes ready-made and what has to be built.
Office: Barajul Dunării 3, District 3, Bucharest