Needset AI

Spend less on AI data. Spend less time on busywork.

Needset builds autonomous systems that do costly work for you and keep a signed record of every decision. Two products, one company. Pick the door that fits.

For engineering and ML leaders

Cut AI data spend

Training data gets copied, re-exported and read again in full by every run. Needset Compiler stores repeats once, sends each job only the data it needs, and proves what that saved.

For founders and operators

Set a goal. Wake up to it done.

Tell Needset Operator the result you want. It plans and does the work, has several AI models check each other, follows your rules for each business, and asks you only when it should, with one tap on your phone.

Most AI data spend is waste nobody can see.

Datasets are re-exported with small edits, copied between buckets and teams, and read in full by every training run. Storage grows, transfer bills grow, and GPUs sit waiting for input. Needset Compiler sits between your object store and your training jobs and takes that waste out in six ways.

Store repeats once

Files are split into pieces by their content, and each piece is stored once, however many files, versions or compressed archives contain it.

Send only what the job needs

Say what a training run needs and its byte and time budget. Needset picks the smallest set of data that covers it, and never resends a piece the job already holds.

Put data where it is cheapest to use

For each piece, Needset chooses the format, storage tier, route and where it is decoded, using your own prices for storage, transfer and compute.

Use cheaper stand-ins only under your rules

Exact data by default. A smaller substitute is used only under a contract you set: a bounded error, or a check an approver recorded for that task.

Learn from every run

Each run reports what it actually moved, decoded and waited on. The next plan is built on those measurements, not on estimates.

Prove the saving

Every plan and every saving is signed and chained into a tamper-evident ledger, so finance can check the number without taking our word for it.

Example from testing26%less storage on a sample of Dolma, a public AI training corpus.
Example from testing88%of data pieces reused between two releases of the same Dolma subset.
Your dataMinutesfor the free scan to measure your own bucket, read-only.

The first two figures are examples from our own testing on public data, not a promise for yours. The free scan measures your data before you change anything.

Start with a free scan. Nothing changes until the numbers say so.

Connect one bucket, read-only

Create a free workspace and give Needset a key that can list and read. The portal shows the exact policy to paste. Needset can never write to or delete from your bucket.

Run the free scan

In a few minutes you see how much of your data repeats and what it costs you each month, at your own storage price, with the platform fee shown beside it.

Turn on the Compiler

Catalog the data, turn on the Compiler, and compile your first plan. Your originals stay where they are, and every decision is explained and signed.

Example plan for one training runSigned and reproducible
Data the run asked for
930 MB across 60 shards
Data it actually needs
594 MB, 27 shards
Bytes shared between shards, stored once
336 MB
Already on the cluster, not sent again
258 MB
Evaluation sets kept out of training
2
Stored36% less
Moved to the cluster64% less
sha256:93724d84e58a7697…Recompiling the plan reproduces the same hash.

An example of the signed plan the Compiler produces for a training run.

The Compiler in 90 seconds.

Where the hidden data bill in AI comes from, how Needset cuts it, and how to start with a read-only scan that moves nothing.

Set a goal. Wake up to it done.

Needset Operator is for people who run businesses and have more work than hours. You describe the result you want. It works on it while you sleep, checks with you when it should, and records everything it did.

You set the goal

Say what done looks like, in plain words. Operator breaks it into steps and gets started.

Models check each other

Several AI models review the work before it counts, so one model's mistake does not become yours.

Your rules, per business

Decide what it may do on its own and what it must ask about, separately for each business you run.

One tap from your phone

Anything that needs you arrives as a short approval request. Approve or decline in one tap, and see the signed record of what it did.

Operator is in early access while we open it to more businesses.

You stay in control.

Both products are built so you can see, approve and check what they do.

Read-only by default

The Compiler reads your bucket and never writes to it. Originals stay until a named approver retires them, and rollback restores the old path.

You approve what matters

Pilots, retirements and Operator actions outside your rules wait for a person. The approval is recorded with who gave it.

Signed records

Plans, savings and activity are signed and chained, so a change after the fact is detectable. Anyone with the public key can verify them.

Your data is not training data

We never use customer data to train models. Run the Compiler hosted, in your cloud, or fully self-hosted.

Proof in public

We run our own autonomous system with real money, in the open.

Needset Markets trades the company's own capital and publishes every decision to a signed public ledger, so anyone can check what an autonomous Needset system did and when. It is not an investment product or advice, and it can lose money.

Pick a door.

Engineering leaders: see what your training data really costs with a free read-only scan. Operators: join early access and hand Needset your first goal.