Altun Core
TR
02

SAAS DEVELOPMENT

SaaS product development.

Altun Core turns a product that already has users into a multi-user SaaS. Accounts, roles, subscriptions and the admin panel are built as one product, not bolted on one at a time.

Start a projectHow the work runs
Multi-tenant structure
02 / 04
Accounts — Roles — Subscription

Technologies used

  • Next.js
  • React
  • TypeScript
  • PostgreSQL
  • Redis
  • Docker
  • Stripe
  • iyzico

Every project starts on the current stable versions; no version numbers are pinned in copy.

Who it is for

For products that are validated and already live in a first version. An application written for a single user has to be rebuilt once teams, roles, plans and billing arrive. This page describes the scope of that step.

Scope

  1. 01Multi-user data model: accounts, teams, and data kept separate between accounts
  2. 02Roles and permissions, enforced on every screen and every API endpoint
  3. 03Sign-in and authentication: OAuth 2.0 or session-based login, all traffic over HTTPS/TLS, API keys kept server-side only
  4. 04Admin panel for users, plans and content
  5. 05Email flows: invitations, password resets, payment and usage notices
  6. 06Usage limits and features that open and close with the plan

For a defined scope, the typical timeline is 8–16 weeks.

Subscriptions and payments

Subscription and one-time payment flows with Stripe and iyzico. With the provider's hosted checkout, card data does not reach your server; if a different flow is needed, PCI scope is discussed at the start of the project.

  1. 01Upgrade, downgrade and cancellation flows
  2. 02Payment events processed through webhooks, with retries and an idempotency key
  3. 03Failed events are recorded and can be replayed

Infrastructure and going live

The application is deployed on a managed platform; in case of an outage, response happens during working hours. Any availability commitment comes from the contract of the hosting provider you choose.

  1. 01PostgreSQL data model and migration discipline, with Redis for caching and queues where needed
  2. 02Docker for an identical environment everywhere, CI/CD for automated deployment

Is it time to grow the product?

Write where the product stands today and which parts are missing. The scope becomes clear in the first conversation.

Start a project