Privacy
Zero-knowledge circuits and confidential transactions, so a product can prove a fact without publishing the data behind it.
- Blockchain
- ZK
Technical services · Senior-led
The technicalhalf of yourcompany.
Your build is stalled. We finish it: senior engineers, a fixed price agreed up front, and code that lives in your repo.
Trusted by teams at
- Polygon
- Ethereum Foundation
- AT&T Labs
- Binance
- Avalanche
- Circularise
- Findora
- QEDIT
- Aztec
- Bolt Labs
- Discreet Labs
- Polygon
- Ethereum Foundation
- AT&T Labs
- Binance
- Avalanche
- Circularise
- Findora
- QEDIT
- Aztec
- Bolt Labs
- Discreet Labs
- Polygon
- Ethereum Foundation
- AT&T Labs
- Binance
- Avalanche
- Circularise
- Findora
- QEDIT
- Aztec
- Bolt Labs
- Discreet Labs
- 3 days
- Written technical brief, in your hands
- In writing
- Scope, boundary and date before work starts
- Day 1
- Your repo, your cloud, your keys
ServicesFixed scope, fixed price.
Fixed scope, fixed price.
Pick the one you need.
Each one has a written scope, a date and a price. Need something working? Start with the POC Sprint. Unsure? Start with the Brief.
01POC SprintStart here
One feature, real code, live on a URL in three weeks.
- Next.js / React
- Postgres
- Typed API
- Vercel / AWS
3 weeks from scope-lock
Read the scope
POC SprintStart here
One feature, real code, live on a URL in three weeks.
- Next.js / React
- Postgres
- Typed API
- Vercel / AWS
3 weeks from scope-lock
Read the scope
Who it's for
You need to show one thing working to a customer, an investor or your board, and slides won't do it.
What's included
- Week zero: one user, one path, one outcome, locked in writing
- That path built end to end: frontend, real backend, real data
- Deployed to a live URL, with auth and a seeded demo account
- A repo with history and a README a second developer can pick up
- A recorded demo run, plus a costed path-to-production note
You end up holding
A live URL anyone can log into, the repo in your GitHub, and a demo recording for when you can't be in the room.
Not included
Production hardening, scale or SLAs. Payments or compliance. Mobile apps or app-store submission. A second user path.
Guarantee
Scope is locked in writing before we start. If it isn't demo-able at the end of week three, we keep working at no charge until it is.
Book a 30-min scoping call
Production is usually 3–6 sprints, not one. Your closing note lays out that sequence, with a price and a gate on each.
02The Technical Brief
Know what to build and what it costs, before you spend.
- Architecture review
- Build vs buy
- Cost model
- Risk register
3 business days
Read the scope
The Technical Brief
Know what to build and what it costs, before you spend.
- Architecture review
- Build vs buy
- Cost model
- Risk register
3 business days
Read the scope
Who it's for
You have a spec, a half-built codebase, or an agency quote you don't trust, and want a straight answer.
What's included
- 60-minute recorded working session on your product and constraints
- Review of what exists: repo, spec, designs or a vendor's proposal
- Recommended architecture and build sequence, with named risks and mitigations
- A real cost and time range, including the option of not building
- One round of written follow-up questions after you've read it
You end up holding
A 4–8 page brief in your drive. Hand it to any developer or investor.
Not included
Code. Designs. Vendor introductions. More than one codebase or spec.
Guarantee
If it tells you nothing you didn't already know, reply within 7 days for a full refund. You keep the document.
Book a 30-min scoping call
Most briefs recommend one of three next steps: a retainer, one sprint, or a phased plan. The brief names which, and the price.
03One Workflow, Automated
One task your team repeats daily, running without them.
- Tool-calling agents
- Retrieval pipelines
- API integrations
- Retries + alerting
10 business days
Read the scope
One Workflow, Automated
One task your team repeats daily, running without them.
- Tool-calling agents
- Retrieval pipelines
- API integrations
- Retries + alerting
10 business days
Read the scope
Who it's for
Your team spends 20–60 minutes a day on the same copy-paste, triage or data-shuffling.
What's included
- Mapping session on one workflow, with the person who does it now
- Built and deployed on your infrastructure: LLM steps, API calls, glue code
- Connected to up to three systems you already use
- Retries, a dead-letter path, and alerts to a channel you choose
- Loom walkthrough, written runbook, and 14 days of post-launch fixes
You end up holding
A running automation, its source in your repo, and a runbook someone else can maintain it from.
Not included
A second workflow. A UI or dashboard. Model fine-tuning. Systems with no API.
Guarantee
If it doesn't run end to end on your data by day 10, you don't pay the second half.
Book a 30-min scoping call
Workflow two moves faster. The integrations, alerting and deploy plumbing are already yours.
04Contract Sprint
One smart contract, written or torn down before mainnet.
- Solidity
- Foundry
- Fuzz + invariant tests
- Gas profiling
- ZK circuits (Circom / Noir)
12 business days
Read the scope
Contract Sprint
One smart contract, written or torn down before mainnet.
- Solidity
- Foundry
- Fuzz + invariant tests
- Gas profiling
- ZK circuits (Circom / Noir)
12 business days
Read the scope
Who it's for
You're shipping one on-chain mechanism, or holding a contract that needs a hard read before mainnet.
What's included
- Build track: one Solidity contract to spec, full tests, testnet deploy
- Teardown track: line-by-line review up to 500 lines, graded by severity
- Gas notes on hot paths, with before/after numbers where we change things
- Written report: assumptions, trust model, and what an attacker can do
- One walkthrough call, and one revision round within 14 days
You end up holding
The contract and its tests in your repo, or a severity-graded findings report for your auditor.
Not included
A formal audit or certificate. This is pre-audit work, and we say so in writing. Mainnet deploys, key custody, contracts over 500 lines.
Guarantee
Teardown track: if we find nothing above informational severity, you pay half and keep the report.
Book a 30-min scoping call
Build output goes to a formal audit; we name firms and prep the package. Teardown output usually becomes a fix sprint.
05Fractional CTO
A senior engineer checking the work, eight hours a month.
- Architecture calls
- PR review
- Hiring loops
- Decision log
Monthly, rolling · 30 days notice
Read the scope
Fractional CTO
A senior engineer checking the work, eight hours a month.
- Architecture calls
- PR review
- Hiring loops
- Decision log
Monthly, rolling · 30 days notice
Read the scope
Who it's for
You have developers or a contractor, and nobody senior on your side checking what they build.
What's included
- 8 hours a month, tracked and reported. No rollover, no surprise overage.
- Two 60-minute calls a month: architecture, hiring, vendors, roadmap
- Shared async channel, with replies within one business day
- Code and PR review on request, up to 4 of your 8 hours
- Hiring help: JDs, interview questions, final-round technical interviews
You end up holding
A one-page monthly note: every technical decision, the reasoning behind it, and what to decide next.
Not included
Writing the code. Being on call. Managing your developers day to day.
Guarantee
Cancel before day 30 of your first month and we refund that month.
Book a 30-min scoping call
When it turns into "someone needs to build this," it becomes a sprint, quoted from context we already have. No re-discovery fee.
Prices are fixed. Scope is agreed in writing before work starts, and anything new gets its own price first.
DomainsBuilt across
Built across
five domains.
The problems change from one industry to the next. The engineering underneath is the same: prove what's true, keep the rest private, and automate what repeats.
Authentication
Identity and login that verify a person without storing their documents. Anon-Aadhaar is the public example.
- Blockchain
- ZK
Supply chain
Traceability that lets partners check provenance and compliance claims without exposing supplier data.
- Blockchain
Media
Provenance for content: who made it, what changed along the way, and whether it can be trusted.
- AI
- Blockchain
Education
Courses and tooling that teach hard cryptography to working engineers, starting with our own zero-knowledge course.
- ZK
- AI
Emerging Technologies
- Blockchain
- Smart contracts, ZK circuits and rollups.
- AI
- Agents, retrieval pipelines and workflow automation.
- Quantum
- Published research on secure quantum computation.
Why trust us
Scope first.
Then money
moves.
01
Scope in writing
What ships, what doesn't, and the date. You read it before anything is signed.
02
You own everything
Your repo, your cloud, your keys from day one. Leave any time and keep every commit.
03
You meet the builder
No account manager. The engineer on your first call writes your first commit.
04
Public work
Read our code, our published research and our zero-knowledge course before you pay for anything.
If your build is bigger than what we do, you hear that on the first call, with the honest range.
TalksWe show up
We show up
and explain the work.
The team on stage, walking through the cryptography and the tradeoffs in public.
See the photo galleryAnon-Aadhaar: a privacy-preserving identity protocol using Halo2 and Noir
Hridam Basu
QuestionsThe hard
The hard
ones.
01Who owns the code?
You do, from the first commit. Everything lives in your GitHub organisation and your cloud account, with your keys. If you stop working with us, any competent engineer can pick it up the next day.
02Can the scope grow once you've started?
Not silently. Anything outside the written scope becomes a new document with its own price and date, agreed before we build it. You never find unapproved work on an invoice.
03Why should I trust a firm I haven't heard of?
Judge what you can check. Our code is public, you get a written scope before money moves, and everything is built in accounts you own. We're based in India and work global hours, with calls at a time that suits you.
04We already have developers. What do you add?
The layer above them: architecture decisions, code review, sprint discipline, and one person accountable for the ship date. That's usually the Technical Brief or the Fractional CTO retainer, not a build.
05What if you disappear halfway through?
Work lands in your repo continuously, deploys run in your cloud, and decisions are written down as they're made. Engagements last days or weeks, so your exposure is small by design.
06Is three weeks realistic for a POC?
Yes, for one locked user path: one user, one journey, real data, deployed. If your scope can't ship in three weeks, we'll say so in the Brief, before you pay for a sprint.
07What don't you take on?
Compliance-certified healthcare or finance (HIPAA, SOC 2), 24/7 on-call rotations, app store operations, staff augmentation, and quarter-long enterprise programs. If that's what you need, we'll tell you on the first call.
08Can I just buy the brief?
Yes, and plenty of people do. The brief is written so any developer can build from it, including a team that isn't us.
Bring the stalled repo.
Leave with a plan.
Thirty minutes with an engineer, free. You'll hear what it takes to build, what it costs, and whether we're the right people to do it.
If we're the wrong fit, we'll say so on the call.
How it works
- 01
You talk, we listen
What you're building, what's stuck, what you've already spent. No deck from us.
- 02
We scope it out loud
Architecture, sequence, and the parts that will be harder than they look.
- 03
You get it in writing
What ships, what doesn't, the date, and the price. Before anything is signed.
- 04
The plan is yours
Build it with us, in-house, or with someone else. No follow-up sequence.