Software and platforms
Cloud and SaaS development.
We build multi-tenant subscription products and move applications to the cloud.
SaaS (software as a service) is software people use in the browser or an app without installing anything, usually on a subscription.
01 / Definition
What is SaaS and cloud development?
Our cloud and SaaS service turns a software idea into a product that many customers use at once, each seeing only their own data, and that scales and bills properly. It also covers moving existing applications to the cloud.
What separates a SaaS product from an ordinary web application is the layer you do not see: tenant isolation, subscriptions and billing, usage limits, self-service sign-up and round-the-clock monitoring. If these are not built in from the start, adding them later costs far more.
02 / Audience
Who it is for.
- Companies that built an internal tool and want to sell it to others.
- Start-ups building business software.
- Software vendors moving an on-premise product to a cloud subscription model.
- Teams whose self-hosted application has outgrown their servers and their patience.
03 / Deliverables
What we deliver.
- 01
Tenancy model
The decision between separate databases and a shared, partitioned one, and its implementation.
- 02
Accounts and access
Organisations, invitations, roles and single sign-on options.
- 03
Subscriptions and billing
Plans, trials, usage-based pricing and the payment-provider link.
- 04
Plan rules and limits
Which customer can use which feature.
- 05
Back office
An internal panel for customers, subscriptions and support.
- 06
Infrastructure as code
Cloud resources defined in versioned configuration, not set up by hand.
- 07
Automated deployment
Controlled promotion from test to staging to production.
- 08
Monitoring and logging
Alerts and dashboards for errors, performance and cost.
- 09
Backup and recovery
Regular backups and tested restores.
04 / Process
How the project runs.
- 01
Product and revenue model
Who pays, for what, and how; most technical decisions follow from this.
- 02
Architecture and tenancy
Data isolation, scaling and data residency decided.
- 03
First release
Core features, account structure and billing built together.
- 04
Infrastructure
Environments set up in your cloud account, as code.
- 05
Private beta
Real usage data from the first customers.
- 06
Launch
Sign-up opens, monitoring and alerts go live.
- 07
Operate and iterate
The product evolves in cycles, guided by usage.
05 / Technology
Technology choices.
We package applications with Docker and prefer managed services, such as managed PostgreSQL and S3-compatible object storage. The cloud can be AWS, Google Cloud, Microsoft Azure or a provider with data centres in Türkiye, chosen by your team's experience, cost and where the data must live.
If you process personal data of people in Türkiye, transfers abroad fall under Article 9 of the Turkish data protection law (KVKK), so we settle data residency during architecture, not afterwards. We do not reach for microservices by default; for most SaaS products a well-structured modular application is cheaper to build and easier to run.
We do not sell hosting. The infrastructure runs in your account, the cloud bill comes to you and you hold the keys.
06 / Example
Examples from our work.
We designed Kolay Sevkiyat as a service for marketplace sellers. Instead of a monthly subscription, sellers top up a prepaid wallet and pay per printed label, with free reprints. It shows how a revenue model shapes the technical design: the wallet, the transaction ledger and the validation steps are one flow.
BeinStory is live on the web, iOS and Android, and we run it day to day, so we know what operating a live product takes. Both are in our portfolio.
In our portfolio
07 / Pricing
Pricing and cost lines.
SaaS projects carry three separate costs:
- 01
Development
The first release and later cycles, as fixed price per phase or a monthly team.
- 02
Cloud infrastructure
Grows with usage and is paid directly to the provider. We design to keep it visible and predictable.
- 03
Operations support
Monitoring, updates and incident response, offered as an option.
Development cost depends on the level of tenant isolation, billing complexity, integrations, compliance needs and expected load.
Development is priced in a written, itemised quote after a short call about your product and scope.
08 / Questions
Frequently asked questions.
- 01
Who pays for the cloud?
You do, directly to the provider, on an account in your name. We set up cost visibility and alerts for unexpected spikes.
- 02
Can our data stay in a specific country?
Yes. We pick a provider and region that meet your residency needs, including data centres in Türkiye where KVKK or customer contracts require it.
- 03
Does each customer need its own database?
Not necessarily. A shared, partitioned database suits most products and costs less. For large enterprise customers or strict compliance, we can recommend separate databases or environments.
- 04
Can you move our existing application to the cloud?
Yes. We first review the application and its dependencies, then migrate with a plan that keeps downtime low, rehearsed on a test environment first.
- 05
How do you handle subscriptions and invoicing?
We design plans, trials and checkout around your model and connect your chosen payment provider. Official invoicing runs through your invoicing provider.