Have a question? Start here.

We build software and take it all the way to working in production: the engine or database at the core, the platform and the interface (the API) around it, and the website or app people use. We work across seven service areas, and each one has a real project behind it that you can read. We take on work when the goal is to ship something finished and reliable, not to run an experiment.

We are a good fit if you are building software that has to keep working: a regulated system, a product with strict requirements, an institution's website, or automation that runs in production. We do not work as a design agency, we do not rent out developers by the hour, we do not run other people's systems for them as a managed service, and we do not do general machine learning consulting. If your need is one of those, we will say so and point you to a firm that does it well.

We are based in Jeypore, Odisha, India, and we work with clients anywhere. We build websites for institutions worldwide, and we keep call slots open for clients in Europe and North America outside Indian office hours.

Both. Our website work is built for institutions, universities, schools, and regulated organisations, where the rules on accessibility, data protection, and required public disclosures are built into the site from the start rather than added before an inspection. We will build a simpler marketing website for a client we already work with, but a standalone marketing site is not our main offer.

They are our own products, separate from the services we sell. SanadEx is a legal drafting tool for Indian advocates, not yet launched. Arka is software to run an Indian K-12 school, also not yet launched. Aika is the assistant on this website, not something you buy. The services are what we build for you; the products are what we build for ourselves.

Every service area has a real project behind it, with numbers you can check, not a wall of client logos. One project cut a manual task from fourteen hours to under a minute across 3,905 records. Our timetable engine has 183 automated tests. A project for a regulated financial institution runs with access controls enforced inside the database itself. You can read each one in our work.

That project is for a regulated financial institution in India, under a non disclosure agreement, so we can show the design and the build but not the client's name. The detailed technical files are available in full to serious buyers who sign a mutual non disclosure agreement, and we will confirm the client's identity to them on the same terms. We do not name clients we have agreed to keep private.

Because that is what it is, and we say so. The Vikram Dev University site is a demonstration we built ourselves and showed to the university; it was not a paid commission. The CBSE school piece is a design study with the school's name removed. The timetable engine is tested at a school that is not a paying client. We label each one so you can tell paid client work from our own demonstrations.

Yes, and it is designed in from the start. Every project comes with written records of the key decisions, and regulated builds keep a log of who read or changed each record, checked against the same rules that control access. You are not left with a system nobody can inspect.

Real, dated numbers. The security page shows the most recent speed test on the live site, with the date it was run, so it updates with each release. If an older figure came from a test we no longer stand behind, we remove it and say so until we have a fresh result. We show the measured result, not a goal.

On regulated work, data protection is built in from the start: we limit what data is collected and why, handle consent, encrypt sensitive personal data, keep each client's data separated in the database, and keep audit logs. This follows India's Digital Personal Data Protection Act, 2023, and where relevant the Reserve Bank of India's rules on outsourcing and cloud use. The exact controls are written into the contract for each project, and the security page lists what we do and do not cover.

We will be straight about this. We are not SOC 2 audited and not ISO 27001 certified. PCI DSS, the payment card security standard, does not apply to any current project. We run security tests for each project rather than on a fixed schedule for this website. The security page lists what we do enforce and what we do not, side by side.

This is a static website with no server or database behind it, and no customer data stored on it. The only data it handles is what you send us: contact form messages, kept for 24 months, and Aika chat messages, kept for 30 days and then deleted. There are no advertising or tracking cookies and no third party analytics.

Yes. We provide a data processing agreement before work starts, under a mutual non disclosure agreement. It covers what data we process and for how long, oversight of any sub contractors, security, your data rights, cross border transfers where they apply, and written notice of any security incident within 72 hours. Both the contract work and the technical files are shared under a mutual non disclosure agreement.

The storage location is set per project. Regulated work for India stays in India; other work follows the rules of its own country. On the regulated financial project, all storage, computing, and AI processing stayed within India, and raw personal data never left to outside systems. Where data has to move between the EU and elsewhere, we use the standard legal clauses for it.

Not the raw data. On regulated work, the AI only sees data that has been combined, stripped of names, and made anonymous, and it has no route to the columns that hold a person's identity. This is the same rule Aika follows on this site: AI is used where it helps, and the sensitive data stays out of its reach.

Four steps. You send a note, and we reply within one working day. We talk for thirty minutes and follow up with a one page written summary of how we would approach the work. We send a proposal with the scope, the stages, the price, and the timeline within five working days. Then we sign and begin, with a contract and a start within a week. The first conversation is free.

Each project has a clear scope and an end point, not an open ended hire. The overall relationship runs under a master services agreement, the main contract, and each project runs under its own signed statement of work beneath it. We do not work on a monthly retainer, and we do not lock you into depending on us.

You do. All rights in the work we make for you, the code, the designs, and the documents, transfer to you once the project is paid in full. The tools we build for our own use are not sold; what you get is the work we built for you and the engineering behind it.

We hand over a system your own team can run, with the documents, decision records, and operating guides they need. We also offer ongoing support if you want it: we stay available to help your team run and extend the system, on terms set in the contract. You are supported after handover, but you are not forced into a long-term service contract, and you are not locked in.

The contract limits our liability to the fees paid in the previous twelve months, with the usual exceptions for confidentiality, rights claims, data protection breaches, and gross negligence. We do the work to a professional standard, and we do not promise a system is ready for production unless the scope says so. If a confirmed security incident happens during a project, we tell you in writing within 72 hours.

The price depends on the work, so we do not publish a fixed rate card. If you ask, Aika, the assistant on this site, has the pricing and will share it. Every project is then priced in a written proposal, with the scope, the stages, the price, and the timeline, sent within five working days of the first call. The first conversation is free.

We invoice in US dollars, euros, pounds, or rupees, due within 30 days, paid by bank transfer. Late payments carry a fee of 1.5% per month under the contract. The exact figures for your project are in the written proposal, not on this page.

Yes. Ask Aika in the corner of any page; it has the pricing and will point you to the right figure without a sales call. It only suggests a thirty minute conversation if it looks worthwhile, and if you are not ready, it will give you something useful to read instead.

We are a small senior team, and we are growing as the work grows. We use AI coding tools to work faster, but an engineer makes every decision, reviews every change, and records why. Our timetable engine, with 183 tests across the solver, the platform, the interface, the website, and the mobile app, shows that a small senior team can build a complete system.

The founder's background is in aerospace and seven years working in financial derivatives markets. That mix shapes how we build, so the decisions deep in a system and the decisions on its surface are held to the same standard. We take on work that has to be finished and reliable, not left half done.

We reply within one working day, hold the thirty minute call, send the proposal within five working days, and start within a week of signing. How long the build itself takes depends on the work, so we set the timeline in the proposal rather than guess at it here.

The system is built to run without us. It comes with operating guides, decision records, and access controls, and on larger builds the important rules, like who can see which records, are enforced in the database rather than hidden in code a new engineer has to work out. If you want us to stay involved, support is available on terms set in the contract. You are not left stranded, and you are not locked in.

If your project would be better handled by another firm, we tell you and suggest who to talk to. We would rather pass on work that is not a good fit than take it on and do it poorly.