Skip to content
frontier labs

Independent AI lab

general models guess. ours know.

We train small language, vision and video models for one job. They beat general models at it, run on hardware you already own, and the weights are yours.

More vehicles found
2.8×
Wrong labels
31
Parameters each
9.4M
General model 1 car · 2 bottles
Specialist 4 cars · 1 van
Fig. 01 · Seven seconds of drone footage, seen by two public models of the same size. Outside the loupe: YOLO11s trained on everyday photos. Under it: the same model fine-tuned on drone footage.

§ 01 · Why specialists

it saw a surfboard.

A general model knows a little about everything. Give it your job, thousands of times a day, and it guesses. These are its real answers on four photographs from the industries we build for.

A technician in a safety harness stands on the hub of a wind turbine, one rotor blade above him.
Fig. 02a · A wind turbine blade, a technician clipped in beside it. It saw a surfboard, 57%.
A tall steel lattice pylon on a concrete pier in the River Severn estuary, its cables running off across the water.
Fig. 02b · A pylon of the Severn crossing, standing in the estuary. It saw a bench, 58%.
Bags of meringues on a supermarket shelf next to boxed cleaning mops with price tags.
Fig. 02c · Bags of meringues on a supermarket shelf. It saw a donut, 22%.
A red reach truck moving between tall pallet racks in a warehouse, its operator seated.
Fig. 02d · A reach truck between the racks of a warehouse. It saw a refrigerator, 23%.

Real output of YOLO11s, a widely used open detector. Everything it reports above 20% confidence is drawn.

  • Sharper

    A specialist learns from your examples and little else, and it is scored on cases it has never seen.

  • Smaller

    Millions to a few billion parameters. It answers in milliseconds on a laptop, a phone or the camera itself.

  • Yours

    You receive the weights, the recipe and the test set. Nothing to rent back, and your data never leaves.

§ 02 · What we build

three kinds of specialist.

Eighteen model types we know how to make, from a few million to eight billion parameters, and where each one runs. Pick one to start a project with it.

A · Language models 7 types

Fig. 03a · A receipt from 1857, as a document reader first sees it.

From one million to 8 billion parameters, distilled from larger teachers and tuned on your text.

B · Recognition 7 types

Fig. 03b · A circuit board, before inspection.

Detectors from a few million parameters, and vision-language models small enough to fly.

C · Generation 4 types

Fig. 03c · Rail and ballast, the kind of scene rare defects are generated into.

Adapters for open diffusion models, trained on your catalog, your look or your edge cases.

§ 03 · SAM-assisted

the workflow labels. the specialist ships.

Ask SAM, a general segmenter, for the kernels in this photo and it outlines the cobs. Wrap it in a workflow of crops, thousands of point prompts and shape checks, and it finds them all. That workflow is how we label. What we ship is the small model trained on its labels.

One photo, four ways

Ten cobs of multicoloured flint corn hanging side by side, thousands of small kernels in red, yellow, white and purple.

SAM · whole image · 23 masks

Fig. 04 · Corn cobs, every kernel a mask. Pick a method to see what it found.

Real output of SAM 2.1 base, 81M parameters, on one Apple M5 Max laptop. The specialist row is a sample until we publish its measured run; its masks are the workflow's, which it is trained to reproduce.

  • The workflow teaches

    SAM with crops, 23,688 prompts and shape checks outlines every kernel, at minutes of GPU per photo. We run it once, over your examples.

  • The specialist answers

    A few million parameters, trained on those outlines and scored on photos it never saw. One pass, in milliseconds, on the camera that takes the picture.

  • Nothing to babysit

    No prompts, no crops, no agent in the loop. It does one job, it was tested on that job before it shipped, and it gives the same answer every time.

§ 04 · Store attention

every camera can tell you what people look at.

Chain three open models over store footage, one for bodies, one for gaze and one for depth, and you get a map of what shoppers look at. Offline, on a big GPU, with every face in frame. We train that chain into one small model that runs on the camera box, live, and keeps skeletons instead of faces.

A busy supermarket floor, blurred and grey, shoppers between produce stands and fridges.

67 tracks · 11.4 s

Fig. 05 · Eleven seconds on a supermarket floor. People are drawn as skeletons, the footage is blurred until no face can be read, and heat builds where heads point.

Where eyes went Sample

  1. Front fridges 52.2 s 27 looks
  2. Fresh meat counter 33.7 s 17 looks
  3. Household offers 22.5 s 9 looks
  4. Chilled greens 14.5 s 7 looks
  5. Snack shelf 10.2 s 5 looks
  6. Fruit stand 4.7 s 4 looks

The skeletons are real output of YOLO11x-pose, 59M parameters: 67 tracks over 11.4 seconds of footage, every frame, in 15.9 s on one Apple M5 Max laptop. The gaze, the heat and the shelf totals are a sample, estimated from head points, until we publish a measured run.

  • Three models, after the fact

    Pose, gaze and depth models chained over recorded footage: minutes of GPU for every minute of video, and every model sees every face.

  • One specialist, live

    Trained on what the chain produced and tested on stores it never saw. A few million parameters, on the camera box, at the camera's frame rate.

  • Skeletons, not faces

    It keeps seventeen points per person and the way their head points. No faces, no identities, nothing worth leaking.

§ 05 · Where it runs

small enough for anywhere.

Memory is plain arithmetic: parameters times bits per weight. Size a model and see what can hold it.

1.7B
135M671B

Precision

Weights 0.85GB

it runs on a phone.

  • Phone 3 GB
  • Laptop 12 GB
  • Desktop GPU 22 GB
  • Data-center GPU 75 GB
  • Cluster Any size

Weights only. Allow 10 to 30% more for context and runtime.

§ 06 · How we work

it ships only if it wins.

Every project runs the same three steps, and the second never starts without the first.

  1. 01

    Measure

    We build a test set from your real cases, lock it away from training, and score what you use today on it.

  2. 02

    Train

    A large teacher drafts labels, your experts correct the hard ones, and a small open model learns from both.

  3. 03

    Ship

    Same test set, side by side. If the specialist does not win on the numbers you chose, it does not ship, and you keep the report.

Fig. 06a · A sample run for a receipt reader. The figures are illustrative.

The handwritten 1857 receipt with a box around each line the OCR model found, labelled with what it read.

What step 01 measures Indra OCR 1.1.2 · 93 ms on CPU

It readThe page says
Sray sulle June 1857 Braggville June 1 1857
Albert Steen bought of Albert Stevens bought of
P. Harbehoon D. Hartshorn
56 ft. Milk 14. 36 qts Milk 4
heceived day Received pay
199 144
I Hartaliare D. Hartshorn

13 of 19 words wrong

Fig. 06b · The same receipt, read by Indra OCR 1.1.2, a general OCR model with a 1.3M-parameter recognizer, in 93 ms on one Apple M5 Max laptop CPU. Real output, every line as it came back. Fast and small, and it misreads the buyer, the seller and the quantity: that is the score the specialist has to beat.

§ 07 · Open weights

the weights are yours.

Client models ship as files you own and run anywhere. Some of what we learn we publish, in exactly the same form.

frontierlabs / ledger-1.7b

Text to JSONApache-2.01.7B
1
model.safetensors3.44 GB2
ledger-1.7b-Q4_K_M.gguf1.11 GB3
mlx-4bit/0.98 GB
ledger-1.7b.onnx1.32 GB
recipe.yaml6 KB
eval/report.json41 KB

Model card

Reads printed and handwritten receipts, invoices and ledgers into JSON. Base model Qwen3-1.7B. Trained on 140,000 synthetic and 9,000 hand-checked documents in six languages.

Limits. Weak on carbon copies and on tables that continue across pages.

4

Evaluation · held-out set

Field accuracy
95.8%
Exact document match
88.1%
Tokens per second, M3 laptop
74
5

llama-server -hf frontierlabs/ledger-1.7b-GGUF

6
  1. 1

    A licence you can ship

    Apache-2.0, with the base model's licence checked before training starts.

  2. 2

    The weights themselves

    Full precision and 4-bit builds in safetensors. Nothing behind an API.

  3. 3

    Builds for every runtime

    GGUF for llama.cpp, MLX for Apple silicon, ONNX for everything else.

  4. 4

    A card that admits limits

    What it was trained on, what it is for, and where it fails.

  5. 5

    An evaluation you can rerun

    The held-out set, the harness and the recipe. Retrain it yourself.

  6. 6

    One command to run

    On a laptop, offline, with tools you already have.

Our releases

  • Ledger 1.7B Receipts, invoices and ledgers into JSON Preview
  • Overhead S Vehicles and people in drone footage Training
  • Reel Embed 300M Search video by describing the moment Planned

Follow releases on Hugging Face.

§ 08 · Pricing

start with a study.

Two weeks on your data, at a fixed fee. At the end you know, with numbers, whether a small model beats what you use today, and what it costs to build.

Feasibility study

€8,000

Fixed fee, two weeks

  • Your current system scored on your own cases
  • A prototype specialist and its results
  • A go or no-go, in writing
  • A fixed quote for the build, minus the study fee
Book a study

Builds usually take six to ten weeks. Retraining and support are billed monthly.

§ 09 · Questions

questions, answered.

The ones every first call starts with.

01Who owns the model?

You do. You receive the weights, the training recipe, the evaluation set and the serving code. We check the base model's licence before we start and only build on ones that allow commercial use.

02Will our data end up in your open models?

No. Client data trains client models and nothing else. Our open releases are trained on public and synthetic data, and each model card lists exactly which.

03How much data do we need?

Usually less than you think: a few hundred labeled examples for a narrow text task, a few thousand images for a detector. A larger teacher model can generate more, and your experts correct the hard cases. The study tells you what you have.

04How small can it get?

That depends on the job. Extractors and classifiers often work at 0.5 to 2 billion parameters, detectors at a few million. Many of our models run on a CPU, a phone or the camera itself.

05What if a general model does better?

Then we say so, and the study tells you before you spend more. Both systems are scored on the same held-out cases, and a specialist ships only if it wins on the measures you chose.

06Can it run without the internet?

Yes, and that is often the point. We deliver containers for vLLM, llama.cpp, ONNX Runtime and Core ML, and models run air-gapped on your servers or on the device.

07Who looks after it once it is live?

You can: the recipe is yours. Or we retrain it on a schedule as your data drifts, and watch its accuracy in production, under a monthly support plan.

§ 10 · Contact

tell us the job.

One sentence is enough. Within two working days we reply with whether a small model can do it, and what it would take.

Opens your email with the task filled in.

Frontier Labs © 2026