Skip to main contentSkip to navigationSkip to footer
    Web & Apps · Service

    App, database, login.
    One build.

    A custom CMS, a web application or an Expo mobile app on Supabase: a Postgres database, user accounts, file storage and live updates. Designed, built and deployed by the same people, in accounts you own.

    See pricing
    At a glance
    From ₹0,00,000 + GST
    Custom CMS, web application or Expo app. Typical plan: 5–8 weeks
    0+
    Projects since 2019
    Postgres
    A standard database, yours to export
    WHAT'S INCLUDED

    Front end. Back end. One scope.

    Screens, tables, roles and integrations are listed in the written scope before a line of code is written.

    The application
    01
    Web application or custom CMS in React and TypeScript, or an Expo (React Native) app for iPhone and Android, with up to 6 screens designed first and two revision rounds
    02
    Admin area for managing users and content. For a custom CMS, this is the editor your team writes in
    03
    Live updates through Supabase Realtime, on the screens that need them
    04
    Server data fetched and cached with React Query
    05
    Loading, empty and error states on every screen
    The backend
    01
    Postgres database on Supabase, with the schema written as migrations
    02
    Login by email, magic link, Google or phone OTP, with up to 2 roles
    03
    Roles and permissions enforced by row-level security policies
    04
    File uploads in Supabase Storage, with access rules per folder
    05
    Up to 6 tables. Edge Functions for webhooks and email, and one payment or email integration
    06
    TypeScript types generated from the database schema
    Handover
    01
    Supabase project in your organisation, repository in your GitHub
    02
    Every schema change as a migration file in the repository
    03
    A written list of every table, policy and function
    04
    CI/CD: a preview URL for every change, production on merge
    05
    A recorded walkthrough of the app, the admin and the Supabase dashboard
    06
    A 30-day window after launch for fixes to anything delivered
    WHAT IT COSTS

    One build. From ₹1,00,000.

    The starting scope covers front end and back end together: up to 6 screens, 6 tables, login, 2 roles and one payment or email integration, with two rounds of design revisions. Bigger scope is quoted in writing. Supabase and hosting bill you directly, and the scope states what they will cost to run.

    ₹0,00,000 + GST
    Starting scope: up to 6 screens
    Up to 6 tables, login, 2 roles, one integration, two revision rounds. More is quoted separately.
    0–8 wk
    Typical plan
    From signed scope to production. The scope sets the date.
    0 min
    First call
    The users, the data and what each role may do, then a written scope.
    HOW LONG

    Data first. Then screens.

    A typical plan. Tables, roles and integrations move it. Work beyond the starting package is scoped and dated separately.

    01
    Week 1

    Schema design

    Data modelled, relationships drawn and security policies planned. Screens and user flows agreed in writing.

    02
    Weeks 1–2

    Backend setup

    Supabase project created in your organisation. Tables, row-level security, login providers and storage configured.

    03
    Weeks 2–5

    Frontend

    React screens built on the live schema, with real-time features, on preview URLs you can open any day.

    04
    Weeks 5–8

    Security review and launch

    Every policy tested as every role, edge cases worked through, then production and handover.

    IF IT GOES WRONG

    The data stays yours.

    In standard Postgres, exportable on any day.

    01

    Standard Postgres

    Supabase is open source and runs plain Postgres. The database can be exported and moved to any Postgres host.

    02

    Security at the database

    Row-level security sits on every table. A mistake in the frontend cannot show one user another user's rows.

    03

    Every schema change on record

    Each change to the database is a migration file in your repository, with a date and a reason.

    04

    Daily backups

    Supabase's paid plans back the database up every day, restorable from the dashboard.

    05

    Scope in writing

    Screens, tables, roles and integrations are listed before the build. A change is priced before it is made.

    06

    Bugs fixed

    Anything in the delivered scope that does not work as agreed is fixed as part of the build.

    WHO IT'S FOR

    Apps with users. Not pages.

    If the second list sounds like you, another page here fits better.

    This build fits

    • 01
      The first version of a SaaS product

      Accounts, teams, roles and billing, on Postgres from the first day.

    • 02
      A loyalty, rewards or subscription app

      Customer accounts and balances next to a D2C store.

    • 03
      A community platform

      Posts, replies and notifications that appear as they happen.

    • 04
      An internal business tool

      Inventory, CRM or operations, with a role for each person.

    • 05
      A custom CMS

      An editor built around your content, where an off-the-shelf CMS does not fit.

    • 06
      A mobile app in Expo

      One React Native codebase for iPhone and Android, on the same Supabase backend.

    Look at another page first

    • 01
      It is a website of pages to read

      Website Development, from ₹10,000 for a single page and ₹50,000 for up to 10 pages.

    • 02
      You only need an installable web app

      A progressive web app is ₹35,000 per application.

    • 03
      It is a shop

      Shopify already holds the catalogue, the orders and the checkout.

    STANDARDS YOU CAN CHECK

    Tested as each role. Then launched.

    Each one is checked before launch, and the evidence comes with the repository.

    01

    Row-level security on every table

    No table is readable without a policy. The list of policies is in the handover.

    02

    Policies tested as each role

    Before launch, every role signs in and tries to read and write what it should not.

    03

    No service key in the browser

    The frontend holds only the public key. Privileged work runs in Edge Functions.

    04

    Types from the schema

    TypeScript types are generated from the database, so a renamed column fails the build.

    05

    Migrations, not dashboard edits

    The production schema matches the migration files in Git.

    06

    Keyboard and screen reader

    Menus, dialogs, tables and forms work without a mouse, with labels and visible focus.

    BEFORE YOU BRIEF

    What founders ask about the backend.

    It is where a custom CMS, a web application or an Expo (React Native) app starts: up to 6 screens, up to 6 tables, login with up to 2 roles and one payment or email integration, with two rounds of design revisions, deployed and handed over. Bigger scope is quoted in writing before any work starts.
    An open-source backend built on PostgreSQL. One project gives an app its database, user accounts, file storage, live updates and server-side functions. The React app talks to it directly, so there is no separate backend codebase to write and host.
    The database is PostgreSQL, which has run production systems since the 1990s. Supabase adds managed hosting, daily backups on its paid plans, and a dashboard. What decides whether an app is ready is the schema, the security policies and the testing, and those are the larger part of this build.
    Yes. The data is standard Postgres and exports with the usual Postgres tools to any Postgres host. Supabase itself is open source and can be self-hosted. The schema is kept as migration files in your repository, so it can be rebuilt anywhere.
    Supabase and the hosting provider bill you directly. Supabase's entry plan pauses a project after a week without activity, so a production app runs on the Pro plan, currently from $25 a month, with usage above its allowances charged on top. The scope states the expected monthly cost for the volumes you name.
    At the database. Every table has row-level security policies, so a signed-in user can read and write only the rows the policy allows, whatever the frontend asks for. Before launch, every role signs in and tries to reach what it should not. The list of policies comes with the handover.
    Larger database sizes and read replicas are a plan change on Supabase, not a rewrite. The schema and its indexes are designed for the volumes named in the scope, and slow queries are found in the dashboard's query reports.
    Yes. A payment gateway such as Razorpay connects through Edge Functions and webhooks, so keys stay on the server and the database records every payment event. The starting scope includes one integration, a payment gateway or email. Each further one is listed and priced in the scope.
    You do. The Supabase project sits in your organisation, the repository is in your GitHub, and the hosting account is in your name, all from the first day.
    Anything in the delivered scope that does not work as agreed is fixed as part of the build. After that, further features are quoted in writing, or the app is handed to your own developers with the documentation.
    3 SERVICES · WEB & APPS

    More in Web & Apps.

    App, database, login.
    One call.

    Thirty minutes on what the app has to do. A written scope after it, with the running costs.

    See pricing