Money moves when you approve, not before
Funds are held against each milestone and released when you accept the work. Not on a schedule, not on an invoice date — on your approval.
The enterprise practice of Pixirain
Custom platform engineering, AI systems, assurance and data-protection work for organisations whose problem does not have a product. Scoped to one company at a time, delivered on escrowed milestones, with a single name answering for the outcome.
The thesis
Everyone is shipping. Almost nobody is checking.
Assurance is not a side practice here. It is the layer we think the market is missing — the one that answers for whether any of what has been built is actually any good — and it is why a firm that builds systems also audits, certifies and red-teams them.
AST & Symbolic Proof
De-synthesizes hallucinations.
Red-Team Fuzzing
Stress-tested boundary limits.
Client Release Gate
Zero automated deployment.
What we do
The delivery rail
Custom work usually fails on process, not on capability. So the process is not improvised per engagement — it runs on the same infrastructure the catalogue business has been delivering on, and these four properties are structural rather than promised.
›
Funds are held against each milestone and released when you accept the work. Not on a schedule, not on an invoice date — on your approval.
Work is assigned rather than tendered, and the assignment carries accountability with it. If the wrong person was chosen, that was our decision to make and ours to fix.
Every deliverable is a first-class record with a type, a version, a reviewer and a revision history. Nothing important lives in a chat message.
A delivery lead is attached to the engagement and answers for it. Escalation is a name, not a support queue.
Engagement
Everything here is scoped to one organisation, so a number on this page would be a number about somebody else. What can be said in advance is how the commitment is structured — and that is a more useful thing to know first anyway.
Scope agreed up front and priced as a whole. Funds sit in escrow and release against milestones you approve, so payment tracks delivery rather than elapsed time. The usual shape for a build with a known destination.
Fits
A system with a clear definition of done.
Engineers, designers and a delivery lead operating in your tooling, your standups and your review process, with one accountable owner on our side. For work where the scope moves because the problem is still being understood.
Fits
Work that will change shape as it goes.
A recurring engagement for organisations that need continuous review rather than a one-off report: re-certification as the codebase moves, obligations tracked as regulation changes, and remediation capacity held ready.
Fits
Obligations that do not stop moving.
For agencies, consultancies and independent consultants who own the client relationship and need capacity behind it. Escrowed milestones and named accountability apply to your clients exactly as they would to ours, invisibly.
Fits
Firms constrained by capacity, not demand.
Available selectively, and only where the outcome is measurable and we control enough of the delivery to be accountable for it. It requires underwriting on our side, so it is a conversation rather than an option to select.
Fits
A measurable result we can genuinely influence.
Governance · India
India’s Digital Personal Data Protection Rules were notified on 13 November 2025. Full substantive compliance — notice, consent, security safeguards, breach reporting and data-principal rights — becomes enforceable eighteen months later.
Until 13 May 2027
No threshold
Nothing about turnover or headcount decides whether you are in scope. Recognised startups can be notified out of a handful of obligations — never out of the Act.
One field
Collecting a name, phone number or email digitally makes an organisation a Data Fiduciary.
₹250 crore
The ceiling for failing to keep reasonable security safeguards. Penalties are set per violation category, so one incident can draw several.
MeitY published the Rules. The provisions constituting the Data Protection Board came into force the same day.
Rule 4 comes into force, governing Consent Manager registration, eligibility and obligations.
Eighteen months after notification. Notice, consent, security safeguards, breach reporting and data-principal rights all become enforceable.
What happens next
A working session, not a sales call. We map what exists, what it has to become, and what would make the project fail. You leave with that written down whether or not you engage us.
The scope becomes milestones with acceptance criteria attached to each. Ambiguity gets resolved here, in writing, because it is the only place resolving it is cheap.
Work runs in a shared workspace you can watch. Each milestone is submitted, reviewed and approved by you before the next one is funded.
Source, credentials, infrastructure definitions and decision records transfer to you, and stay recoverable afterwards. An engagement that ends should not strand anything.
Start here
Not a demo request and not a qualification call. A working session that maps the problem — and you keep that map whether or not you engage us.