From research paper
to running product.

Rump Labs is a product company built on R&D. We research, prototype and ship systems across AI, cryptography, blockchain and quantum, and consult for the teams building them.

Rump Lab · Overview
lab.rumplabs.xyz/projects/identity-layer/overview Live · sample data
OverviewSample project · week 2 of 3
11.9kConstraints, from 18.4k
1.8sProof generated
214Tests passing
96.4%Agent eval score
2Open risks, named
MilestonesScope locked in writing
MilestoneOwnerStatus
Attribute circuit (Noir)ResearchDone
Verifier contractEngineeringDone
Demo path on a live URLEngineeringRunning
Proving timeAcross 16 builds
−42%

The team has worked with

PolygonEthereum FoundationAT&T LabsBinanceAvalancheCirculariseFindoraQEDITAztecBolt LabsDiscreet Labs

On the stack the field already runs

EthereumSolidityRustTypeScriptPythonPyTorchLangChainQiskitCircomCircomNoirNoirHalo2Halo2
How research becomes product

Four steps from question to product.
We carry three of them.

Step 01 / 04Question

It starts with a hard question.

Yours, in your words.

Can this be proven without the data? Will the agent hold up on real inputs? Is the contract safe before mainnet?

  • Your product
  • Your constraints
  • Your deadline

Then the research.

Written down, in the open.

The maths, the proof system, the threat model. Papers go out open-access, so you can read the thinking.

  • ZK and MPC
  • Quantum
  • Open access

Then a prototype.

On a live URL.

One user, one path, one outcome, built end to end on real data, in your repo from the first commit.

  • Live URL
  • Your repo
  • Scope in writing

Then the product, and the people to run it.

Shipped, then taught.

Production sprints with a price and a gate on each, and training so your own engineers can carry it forward.

  • Fixed price
  • Your cloud
  • Your team trained
See the eight domains
Domains

Eight domains.
One lab behind all of them.

Where the research turns into product. Each one is a set of problems we have already worked through.

How an engagement starts

Four steps before anything is signed.
Scope first, then money moves.

  1. You talk, we listen

    What you're building, what's stuck, what you've already spent. No deck from us.

  2. We scope it out loud

    Architecture, sequence, and the parts that will be harder than they look.

  3. You get it in writing

    What ships, what doesn't, the date, and the price. Before anything is signed.

  4. The plan is yours

    Build it with us, in-house, or with someone else. No follow-up sequence.

Services

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.

$490The Technical Brief→$4,900POC Sprint
  • Scope in writing before work starts
  • Your repo, your cloud, your keys
  • A guarantee that costs us if we're wrong
Fields0frontiers we research and build in
Domains0domains with work behind them
Training0hzero-knowledge curriculum in Gurukul
Talks0stages shared, on record
Get started

Two ways in.
Build with us, or learn from us.

One lab does both, so the people who ship it are the people who teach it.

Build

You need it shipped.

Research, prototypes and production engineering, with a senior engineer accountable for the date.

  • POC on a live URL in three weeks
  • Contracts torn down before mainnet
  • Agents measured on your data
  • A fractional CTO checking the work
Fixed scope and price, agreed in writing before work starts.
Learn

Your team needs to learn it.

Rump Gurukul's 8-module zero-knowledge course, workshops and lectures, taught by the people who build these systems.

  • 40 hours, self-paced
  • No prerequisites
  • Circom, Halo2 and Noir
  • Certificate on completion
Hands-on projects, and a final ZK application of your own.
Questions

Asked before, answered here.

Sorted by what you are deciding. Every answer is something we already do.

Still deciding?

Thirty minutes with an engineer, free. If we're the wrong fit, we'll say so.

Book a call
Working with us5 questions

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.

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.

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.

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.

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.

Next step

Tell us what
you're building.

Thirty minutes with an engineer, free. You'll hear what it takes, what it costs, and whether we're the right people to do it.