THINKINGDBX · MODELS, PIPELINES, AGENTS

AI that runs where
your data is allowed to be.

We train domain models you own, build the self-hosted data platform that feeds them, and run AI teammates on your business data from our cloud. Inside your air gap when the data cannot move, on our infrastructure when it can.

01/

Weights delivered, not licensed

02/

Air-gap capable (Foundry, Studio)

03/

Open weights on Hugging Face

train.internal.acme-bank.corp no egress
Run · acme_9b
✓ corpus
✓ tokenizer
▸ pretrain
○ post-train
○ eval
Corpus
⛃ core_banking
▤ ops_manuals
⌘ pii redacted
step
18,400/24,000
loss
1.847
tokens
93.5B/122B
throughput
47.3ktok/s
warmup spike · recovered
step 0loss, log scaletrainval18,400
14:02:11 ckpt saved runs/acme_9b/step-18400
14:02:11 eval held-out acc 0.94 on your ground truth
14:02:12 egress attempts 0 · weights stay in /mnt/models
on delivery acme_9b.safetensors acme_9b.gguf eval/ yours to keep, yours to serve →
The stack

One stack, from the model to the agent.

Use one layer or all three. Each works on its own.

01/

Domain models you own

Foundry · Models

Domain models trained inside your perimeter, delivered as weights you own outright. A few hundred examples is enough to start.

From $15k · air-gap capable
02/

The data platform that feeds them

Studio · Pipelines

An agentic data platform that ships pipeline code to your Spark and Kafka and serves your models on your own Ollama or vLLM. Self-hosted, air-gap capable.

From $60,000 a year · self-hosted
03/

AI teammates for your data

Kin · Agents

AI teammates that query your databases, check every number, and ask before changing anything. Hosted on our cloud, so there is nothing to install: connect a database and give a kin its first job.

Free to start · Pro $49 a month · cloud
Foundry weights Studio pipelines + serving Kin agents on your data ON OUR CLOUD INSIDE YOURPERIMETER IF YOU NEED IT TO BE
Flagship · Foundry

We build models, and we show our work.

Pretrained from scratch on our own GPUs. Every model ships with evals and a written account of where it fails.

An analyst drops a quarterly filing into context and asks for the segment margin: Kautilyaa returns the figure and the line it came from, or says it does not have that number. Across 150 test cases it produced no invented figures at all.

From the build log

The useful output of a build is rarely the benchmark

On Kautilyaa we traced a silent optimizer bug that had been degrading every run: weight decay applied to normalisation gains, invisible in the loss curve. Catching that class of failure before your compute is spent is what a Foundry engagement is for.

  foundry precheck acme_9b.yaml
# checked before a single GPU hour is billed

P1  weight decay excludes norm gains   BLOCK
     exclusion list is empty: every
     parameter decays, including the
     RMSNorm gains. invisible in loss.

P2  checkpoint interval fits tenure    BLOCK
     10000 steps on spot capacity:
     every preemption restarts at zero

P15 licence permits delivery terms     pass
P16 eval sets decontaminated           pass
P17 tokenizer fertility measured       warn

# 2 blocking. run not started.
Your weights
delivered, not licensed
Zero
third-party AI calls in what we deliver
Air-gap capable
offline install, no callbacks
56
validation checks before delivery
The full Foundry story → Browse the weights

Where it runs is a compliance decision, not a product tier

Built for sealed networks first, available to everyone else.

YOUR DATA 01/ AIR GAP 02/ YOUR HARDWARE 03/ OUR CLOUD

Inside the air gap

Foundry and Studio. Offline install from mirrored images, no licence server, no callbacks. Your firewall rules are the control, not our promises.

On your hardware

Foundry and Studio. On your GPUs, in your data center or your VPC, with our engineers driving the work. For when residency rules bind the data but the network is not sealed.

On our cloud

Foundry builds on our GPUs, and Kin. For teams with no compliance boundary: you bring the domain or the database, we bring the compute.

Read the security page →

Teams whose data legally cannot touch a public cloud

If you can't send your data to a frontier lab, building a model is the only path left.

Defense & government

Classified and controlled-unclassified networks where air-gap is a hard requirement and offline delivery is the only install path.

Banking & financial services

Core banking, transaction, and PII data under supervisory rules that forbid third-party model processing.

Healthcare & life sciences

Patient records and trial data, where auditors care about where the data physically sits rather than how well it is encrypted in transit.

Critical infrastructure

Energy, utilities, and industrial operators running OT networks that are isolated from the internet by design.

For systems integrators and primes

We deliver as a subcontracted line item

If you have a pursuit with an on-premise or sovereign model requirement, we build it under your delivery. Your client ends up owning the weights outright. There is no telemetry and no callback in anything we hand over, so it should clear your security review without argument, and the audit report is written so it can go into your bid as it stands.

Send us the pursuit

Built in the open.

We built these tools to build our own models. Three are open source, so you can read the code before you trust us with a build.

ThinkingLanguageA typed, compiled language where tables, streams, and models are native types.Open source ThinkingMemoryA memory database for agents. Intent goes in, the right context comes out, packed to a token budget.Open source vibeCodeCLIParallel agent fleets and persistent memory for coding and data engineering, in your terminal. Bring your own keys.Free

Read the code on GitHub →

The corpus audit · one week

Start with one honest week.

A free one-week corpus audit tells you whether you need a model at all. Half end with us recommending you don't build.

Not ready for a call? Send the details →

STEP 1

The audit week

Your domain, the data you actually have, and where a build is allowed to run.

STEP 2

Written report

A token budget, a recommended rung, and eval targets. Or the recommendation not to build.

STEP 3

The build

On our GPUs, on yours, or inside your air gap. How a build runs →