Owning your code: later, or from day one

"You own the code" is easy to say and easy to say vaguely. Here are the two ways to own what we build for you, and the list you receive when you do, which is the test for whether ownership is real.

Two ways to own it

Start monthly, own it later. Most owners do not need their own code on day one and should not pay for it up front. You start on the monthly plan with no setup fee. From ₹9,999 to ₹49,999 a month plus GST for teams of up to 25, set by what you need and your team size. Whenever you want to hold your own code, we give you a one time price based on what we built for you. There is no obligation to buy and no deadline.

Own it from day one. For owners who want their own code and IP from the start, this is a custom offer. We learn how your business works first, then offer a one time build fee and a monthly retainer that covers only running it: hosting, upkeep, changes and Ask your business. No price is published for this path because it depends on what we build. Talk to us about owning it.

Either way, your data is yours from the first day and exports free at any time, and you can cancel the plan with one month's notice.

The list, when the code is yours

1. Source code for what we built for you. Back office, app, website, and the scripts that build and deploy them.
2. The repository, in your account. The git history moves to an organisation you own.
3. Hosting in your name. The hosting account, the database and storage move under your billing and your login, or we keep running them for you on the retainer.
4. Domain in your registrar account. The most common way a business loses its website is a domain registered by a vendor who stops answering. Yours stays yours from the start, whichever path you choose.
5. Every credential, in a password manager you control. Admin logins, keys, app store accounts. Shared once, rotated by you.
6. App store listings under your developer accounts. So a future update does not need us.
7. Documentation another developer can start from. How to run it, how to deploy, where the data lives, what each module does.
8. The data model, explained. A diagram and a plain description of the tables, because the data is worth more than the code.

What stays ours, and why we say so up front

Reusable building blocks we bring to every client, the pieces that are not specific to your business, stay ours and are licensed to you for as long as you use the system, including after you leave. We say this on the pricing page in one line so nobody feels misled later. Third party services the system talks to, such as a payment gateway or an SMS provider, stay with their providers under your account.

The test

Ownership is real if you can hand the repository and the documentation to a developer we have never met and they can deploy a change within a week. We build and document to pass that test, and we would rather you know you can leave than feel you cannot.