SaaS platform

SaaS and multi-tenant platform development: one codebase — dozens of companies

Have a working system and want to sell it to other companies? We make it a SaaS: multi-tenancy, super-admin panel, pricing plans, own domains and branding per client, automatic onboarding.

See examples
from $2,999
turning a system into SaaS
3 wks
multi-tenancy for our Fleet platform
1 codebase
for all client companies

01

When it's time for SaaS

SaaS isn't just for startups. Often the product is born from an internal system that has already proved its value.

01

An internal system peers ask for

You built accounting for yourself and partners ask "can we have the same". Time to sell, not copy.

02

Several instances of one codebase

You've already installed the system for several clients separately, and every update hurts on every server.

03

A startup with an MVP

There's an idea and first users; you need an architecture that survives growth without a rewrite.

04

A franchise or network

Branches, dealers or franchisees must work in one system but see only their own data.

05

You need billing and plans

Trial period, plans, feature and user limits, invoices and payment control.

06

Branding per client

Own domain, logo, Telegram bot and settings — without separate code for each.

02

What a SaaS platform includes

Components we implemented in our multi-tenant fleet platform and carry over to your product.

1

Multi-tenant architecture

Per-company data isolation at code and database level, global scopes, protection against cross-tenant leaks.

2

Super-admin panel

Create companies, plans, statuses, "log in as client" for support, usage statistics.

3

Onboarding and sign-up

Self-registration, setup wizard, demo data, team invitations.

4

Plans and billing

Plans with limits, trial period, invoices and PDF receipts, payment reminders, suspension on non-payment.

5

Client branding and domain

Logo, colours, own domain or subdomain, a separate Telegram bot per company.

6

Roles and users

Owner, admin, staff — within the tenant; system admins — outside it.

7

Public landing and leads

SEO product page, request form, demo access, leads to Telegram.

8

Demo tenant and reset

Public demo with nightly data reset so prospects can try the system.

9

Monitoring and backups

Uptime, errors, encrypted backups per company, admin action log.

Don't see your process?

Describe how it works today — we'll propose a module around your logic.

03

Delivered projects

Live systems our clients use every day. Company names are anonymised by agreement.

🔒 fleet.alemi.pro/superPASS 43 tenancy tests17 tables · company_id
SaaS platform2026

Alemi Fleet — fleet management SaaS

A single-company trip tracking system grew into a multi-tenant platform: isolated companies in one DB, an owner panel with impersonation, a demo with nightly reset, a public cargo tracking link and an SEO landing page with a lead form.

43 tenancy tests17 scoped tablesNew company in 1 min
Read more3 weeks
SaaS platform · tenantsCompany 12Company 34 · carrierCompany 41importCcarrier-brand.comown hosting · own domainTrips98Drivers9Payments66✓ live in 1 dayWialonpositions + reportsRuptela FMSpositions + reportsFreetrack1 req / kind / 300 s
Standalone instance2026

A carrier’s own TMS instance in a day: migration from SaaS and any GPS tracker

A carrier outgrew the multi-tenant platform — we move it to its own domain with one command, keeping IDs and passwords, and plug in its tracker: Wialon, Ruptela or Freetrack.

1-command migration3 GPS providersDeployed in 1 day
Read more3 weeks
System development2025

Fleet management system

Replaced Excel with a full-featured system: drivers, vehicles, trips, expenses and payroll. Trip queue with auto-promotion, real-time GPS tracking, monthly P&L reports.

11 modulesReal-time GPS0 Excel files
Read more2 months
In-house product2026

Control Hub — mission control for projects

A personal dashboard for dozens of projects: task kanban, encrypted credentials, finances at a fixed NBU rate, payments with reminders, site monitoring.

10+ modulesReal-time monitoringCtrl+K search
Read more6 weeks

04

How we build SaaS

  1. 01

    System and market audit

    2–3 days

    We assess the current code, define what's common for all clients and what's configuration. Draft the pricing grid.

  2. 02

    Multi-tenancy architecture

    3–5 days

    Choose the isolation model (shared DB with scopes, separate schemas or databases), design the super panel and billing.

  3. 03

    Refactoring for tenants

    2–3 weeks

    Add company as a dimension to all entities, global scopes, tests for cross-client leaks.

  4. 04

    Super panel, onboarding, plans

    1–3 weeks

    Sign-up, plans, receipts, "log in as client", branding and domains.

  5. 05

    Landing and demo

    1 week

    Public SEO page, demo tenant with nightly reset, leads to Telegram.

  6. 06

    Launch and scaling

    ongoing

    First clients, monitoring, backups, growth from feedback.

05

Pricing for your task

Pricing

from $2,999

Turning an existing system into a SaaS with a super panel and basic billing — from $2,999. A new SaaS product from scratch — from $6,000 for an MVP. We estimate after a code audit.

What's included

  • Code audit and isolation architecture decision
  • Multi-tenant refactoring with leak tests
  • Super-admin panel and basic billing
  • Onboarding, demo tenant, landing page
  • Deployment, monitoring, backups
  • Documentation for your team and 30 days of fixes
  • Source code belongs to you

What affects the final price

  • State of the current code and test coverage
  • Isolation model: shared DB or separate databases
  • Payment gateway integration for automatic billing
  • Number of branding settings and integrations per tenant
  • Resilience and scale requirements

06

What we build with

We pick the stack for the task and your team, not the other way round. Code and data are fully yours.

PHP 8LaravelMulti-tenant scopesMySQLPostgreSQLReactInertia.jsNext.jsTelegram Bot APIPDF billingCron / Queue

07

Frequently asked questions

One instance of the system serves many companies, and each sees only its own data. Updates are made once for everyone, not on each server separately.

Deeper dive

From an internal system to a SaaS product

Why most B2B SaaS is born from internal tools

A system built for your own business is already validated by real processes. It doesn't need to guess what the market wants. What remains is making it fit for many companies: isolate data, add sign-up, plans and administration.

Three data isolation models

Shared database with a company column in every table — the cheapest and fastest, fits most. Separate schema per tenant — a compromise. Separate database per client — for enterprise requirements. We start with the first and keep a path to the others.

The super panel — your control centre

Creating companies, plans, "log in as client" for support, usage statistics, suspension on non-payment, receipts. Without it a SaaS turns into manual admin work.

Our case: the fleet platform as SaaS

We moved a fleet management system to multi-tenancy in 3 weeks: company_id on all entities, super panel, manual billing with PDF receipts, GPS provider choice per tenant, separate Telegram bots, a public landing and a demo with nightly reset.

Where to start

Show us the system and tell us who the first prospective clients are. After a code audit we give a plan: what to refactor, which isolation model fits and what it costs to reach the first clients.

08

Other services

Let's turn your system into a product

Show what already works and tell us who you want to sell it to — we'll propose an architecture and a go-to-market plan.

Telegram ↗
Contact

Let's discuss your project

Describe the task — we'll respond within 24 hours