S/03 · Cloud platform track
A multi-tenant platform, architected and deployed.
Architecture design and backend for a cloud-based platform: a multi-tenant database with real data isolation, secure authentication and subscription logic that keeps access in step with billing — running in production on your own cloud account.
Net price, payable in one transfer before delivery. IT Julian Soft SIA is not registered as a VAT payer, so invoices carry 0% VAT.
[ 01 ] What this covers
The four lines that go on the invoice
Scope, execution, result and deliverable are written down before work starts, and they are the same four lines you will read on the quote.
Scope
Architecture design and backend for a cloud-based platform.
Execution
Multi-tenant database, secure authentication, and subscription logic.
Result
Scalable, secure cloud workspace tailored to the business model.
Deliverable
Production SaaS deployment on cloud (AWS/DigitalOcean/GCP).
[ 02 ] What you get
Eight parts of a working platform
A SaaS product is a set of decisions about data, identity and money. These are the ones that get made, built and documented.
Architecture design
The domain model, the service boundaries and the tenancy strategy, written down and agreed before the first migration is run.
Multi-tenant database
One schema, many tenants, with per-tenant data isolation enforced in the queries themselves — not left to the interface to remember.
Secure authentication
Hashed credentials, server-side sessions or signed tokens, password reset and optional two-factor authentication on the accounts that need it.
Roles & permissions
Owner, member and read-only roles as standard, extended to match your product. Every check runs on the server, never only in the UI.
Subscription & billing logic
Plans, trials, upgrades, downgrades and renewals, wired to your payment provider so that what a tenant can do follows what they pay for.
Admin tooling
An internal panel for tenants, users, plans and support access, so day-to-day operations do not require a developer or a database client.
Production deployment
Released to your AWS, DigitalOcean or Google Cloud account with SSL, DNS, backups and basic monitoring configured.
Environment config & secrets
Separate staging and production environments, with keys and connection strings held outside the repository and rotated at handover.
[ 03 ] How it ships
Five stages, in this order
Data model first, money last. Nothing is built on top of a structure that has not been agreed, and nothing goes live before the environments are separated.
Architecture & data model
We map the entities, the relationships and the tenancy strategy, then write them down. You approve the model before any schema exists.
Tenancy & authentication
The multi-tenant schema goes in with isolation enforced at query level, followed by registration, login, sessions and password reset.
Subscription logic
Plans, trials, upgrades, downgrades and renewals connected to your payment provider, with entitlements derived from the billing state.
Hardening & environments
Server-side role checks, rate limiting, encrypted secrets, backups, and a staging environment that mirrors production without sharing its data.
Production deployment & handover
Deployment to your cloud account with SSL and DNS in place, then a walkthrough of the architecture, the admin panel and the credentials.
[ 04 ] Included
Included in the fixed price
Everything below sits inside the quoted figure. Third-party costs — cloud hosting, domains, payment provider fees — are billed to you directly by those providers.
[ 05 ] Client feedback
From an S/03 engagement
“Every customer now sits in its own isolated slice of the database, and I was shown exactly where that boundary is drawn and how it is enforced. Subscriptions renew, upgrade and lapse on their own — nobody is reconciling a spreadsheet at month end. It was deployed into our own DigitalOcean account, so the platform and the data stay with us.”
[ 06 ] Questions
Before you write in
AWS, DigitalOcean or Google Cloud. If you already have an account with one of them, we deploy there. If you do not, we recommend one based on what the platform actually needs — a small workspace application and a data-heavy one do not belong on the same setup — and you open the account in your company's name.
We build the subscription logic — plans, trials, upgrades, downgrades, renewals and the entitlements that follow them — and connect it to a provider such as Stripe or PayPal through their hosted checkout and webhooks. The merchant account is opened in your name, and card data never reaches the platform's own database.
You do. The cloud account, the domain, the database and the repository are all in your name, and you hold the root credentials throughout. We work with access you grant us, and that access can be revoked the moment the handover is complete.
Yes — a custom module bolted onto something already running is a common version of this service. We review the current schema, code and deployment first, then scope the module against what is there. If the existing structure makes safe multi-tenancy impossible without changes, we say so before quoting rather than after.
[ 07 ] Related services
The other two tracks
E-Commerce Platform Deployment
Setup and deep customization of an online store application — product catalog database, shopping-cart logic and inventory sync, wired to a live payment gateway.
Landing Page Development
UI/UX design and frontend for a conversion-focused single page — clean HTML/CSS/JS with a lead-generation form, a database behind it and analytics on top.
S/03 · From €1 500
Describe the platform you need.
Tell us who the tenants are, what they should be able to do and how you intend to charge them. You get a written architecture summary and a fixed price back.