We build the systems that move public money and public work. The In is India.
Collection, disbursement, treasury, procurement, governance. 27 of our platforms are in production with government bodies, authorities and public sector undertakings, and the audit trail in each one reads back to a name, a time and the record it touched.
A new deployment is configuration, not a rebuild
Underneath the 37 products there is one platform. A workflow engine in which every step has a named seat and a clock. A permission model in which the person who prepares a record and the person who approves it are two different people. An event log that is appended to and never overwritten, each entry carrying an actor, a time and the record it touched.
What changes between a property tax deployment and a subsidy disbursement is configuration: the seats, the approval chain, the rate and penalty rules, the file formats a bank will accept, the receipt layout, the language on screen. The spine does not change. That is why a body that has already chosen one of our platforms gets a working system in weeks rather than a pilot that runs for a year, and why an officer who has used one of them can find their way around the next one.
It also fixes the limit, and we would rather say it early. If your process needs something the engine does not do, that is new build. It is quoted as new build, with its own time, in the first meeting. We would rather lose a month of enthusiasm then than a year of it later.
What the 37 products actually cover
Every one of them is built. Its own page says plainly whether it is in production, onboarding its first deployment, or awaiting a first deployment, and what it does not do.
Money coming in
Property tax, electricity and water billing, waste collection charges, rent and lease on public property. Counter, field and online payment, arrears that age on their own, and a daily reconciliation of counter total, system total and bank credit.
Money going out
Benefit transfer, subsidy, compensation for acquired land, accident claims, rent paid out to lessors. Beneficiary lists in whatever format the department already produces, duplicates matched, files built for the bank's own channel, and the outcome of every lot read back: sent, credited, bounced, retried.
Treasury and monitoring
Income and expenditure against the sanctioned head, budget tracking, project surveillance with milestones and payments in one view. These answer what has actually been spent, which is a different question from what was allotted.
Bank instruments
Bank guarantees on paper and electronic guarantees through NeSL, held in one register against the contract each of them secures. Validity and claim dates are counted from the source record, and invocation, amendment, extension and closure are raised from the record itself.
Procurement and governance
Tenders, auctions, lotteries for allotment. Dak and file movement, legal cases, grievances, public appointments. The work of a department that is not money but is still a deadline with a name against it.
Sector platforms and workforce
Ticketing for monuments and events, guest house booking, parking, clubs, societies, temples. Payroll, inventory, service and assessment for the staff who run all of it.
A record the administrator can quietly edit is not a record. It is a claim.
What a secretary and a bank's risk officer check first
Four answers, given before they are asked for.
Two different people, every time
Maker and checker are separate seats, not a setting someone switches off in a busy month. The clerk who prepares a disbursal file or a guarantee invocation adds a remark and forwards it. The approving officer can approve it or send it back with a reason that is stored, and cannot edit it. Where money moves or a security is given up, there are two names on the record.
A log nobody can tidy
Every action writes an entry: who did it, from which account, at what time, against which record. Entries are appended, never overwritten, and the system administrator has no more power over the history than a counter clerk has. When an audit arrives, the department prints the history instead of reconstructing it from memory and email.
Integrations already carrying live traffic
Payment gateways on the collection side. NeSL for electronic bank guarantees, with the notification endpoint hosted here and every outgoing request digitally signed. Secure file transfer for the batch files banks accept.
On disbursement the platform runs its own two checks, that each record carries exactly the sanctioned amount and that one person is paid once, and passes the list to the bank unchanged. Aadhaar and account verification is the bank's, done before it credits anyone. We do not claim it as ours.
Status, in the plain word
Of the 37 products, 27 are in production, two are onboarding their first deployment, and eight are built and awaiting a first deployment. Each product page says which, in those words. A pilot presented as a running deployment costs a department a year, and it is the fastest way we know to lose a client we would otherwise have kept for a decade.
The four questions that come up in the first meeting
Can we see one of these running in another department?
No, and that is deliberate. We do not name a client, a department, a bank or a city, here or in a meeting. What we will do is run the platform end to end in front of you on test data, for as long as you want to sit with it, using your own process as the script.
The rule that keeps another body's name out of your meeting is the rule that keeps yours out of the next one.
Is this Indian software, or a foreign platform with your name on it?
Indian. The company is Indian, the engineering team is in India, and the code in these platforms was written by that team over eight years and more. Nothing here is a foreign product in a local wrapper, so changing a workflow, a file format or a language for you is a decision taken in this building and not asked of anyone abroad.
How long until it is live?
For a product already in production, plan in weeks: configuration of seats, rules, rates and formats, then one full cycle run beside the existing way with both sets of numbers reconciled at the end of it, then cutover. If the two sets do not agree, we fix the system, not the report.
For a product that is built and awaiting its first deployment, add the time for that first live cycle. You will hear that in week one, not in week ten.
What do you not do?
We do not sell hardware. We are not a payment aggregator and we never take custody of public funds: money moves through the body's own banking channel, and we record it, route the approvals and reconcile it. We do not verify identity, and where Aadhaar or account verification is required the bank performs it. Eligibility and enrolment, where a government portal already owns them, stay there.
Describe the process. We will tell you which platform it is.
Most departments arrive with a process that has stopped moving, not with a product name. Tell us who touches the file, in what order, who signs it, and where it stalls. You will get a straight answer: this is one of the 37, this is one of them plus new build, or this is not us.