// about · godengine systems

A reasoning substrate, built deliberately.

Godengine is a self-hosted decision-intelligence platform. Not a wrapper around someone else's model — a 600,000-line reasoning substrate of 404 cognitive organs across 9 capability layers, built by a small team that wanted to answer the questions a single model cannot.

// thesis

The decisions that matter most are the ones a single model cannot make.

A language model gives you one answer. The decisions that move organizations — capex, M&A, compliance, crisis response — need parallel reasoning that independently models risk, cost, ethical constraint, and second-order effects, then converges them into ranked, auditable scenarios. That is the layer we built.

// real-world questions

The kind of question we exist to answer.

Four production runs from the last six months. Different industries, different stakes — the same coupled-systems structure underneath.

U01 · BFSI
Mid-market bank · Mumbai · Tier 02

Reserves adequacy across a synthetic 1-in-250-year tail.

The treasury team had a stochastic model and a regulator deadline. The engine ran 47,000 nested scenarios with coupled credit-market-liquidity stress in 14 minutes — and signed every output.

47Kscenarios
14 minwall clock
2 wks → 14mvs. prior cycle
U02 · MFG
Auto-tier-1 supplier · Pune · Tier 02

Capex pacing under simultaneous demand softening and FX volatility.

Three lines, two currencies, one closing window. The orchestrator coupled a discrete-event production model to a stochastic FX path and a working-capital constraint. 23 candidate sequences. One survivor.

₹186 Crcapex modeled
23 → 1candidates
9.4%IRR uplift
U03 · HEALTH
Multi-specialty hospital chain · Chennai · Tier 03

OT scheduling under epidemiological surge and staffing constraint.

Surge model from the epidemiology pack, scheduling from operations, ethical constraints from the policy pack — composed live, replanning every 45 minutes for six weeks. Zero deferred urgent cases.

6 weeksdeployed
+18%OT utilization
0deferred urgent
U04 · ENERGY
State utility · western India · Tier 03

Day-ahead dispatch with adversarial price-bid scenarios.

The Adversarial layer red-teamed every dispatch against 31 plausible price-manipulation strategies. The orchestrator picked the schedule that minimized regret across the worst quartile. Audited weekly.

31adversaries
−4.8%regret-worst
100%audit-pass
// origin

How a question became 600,000 lines of code.

The project started as a thought experiment: what if the seven forces that govern every system in nature — intent, friction, momentum, constraint, volatility, coupling, provenance — could be modeled as composable reasoning channels, each with its own cohort of specialists? That sketch became a single Python file. The single file became 404 cognitive organs across 9 capability layers.

We rejected the obvious shortcuts. No LangChain. No LLM gateway. No rented brains. Every organ computes a real metric — physics, economics, epidemiology, causal inference, ballistics — chosen for the job, composed by the orchestrator, adversarially constrained by the convergence layer.

The result is 600,142 lines of proprietary code running on a substrate that nothing else looks like. It is fast, it is auditable, and it is yours when you deploy it — keys, weights, traces, all inside your perimeter. The orchestrator never phones home. There is no shared model. There is no fleet learning loop. Every deployment is a forked, sealed organism.

We are building it from Bengaluru, for the world. We onboard mid-market first because that is where the unmet demand is — and because the most consequential decisions are not made in San Francisco boardrooms. They are made in factories in Pune, in trading floors in BKC, in hospital admin rooms in Hyderabad, in policy cells in Delhi.

FILE · arch.dag● recording
// where we stand

As of v2.2.

Eight numbers we'd be willing to defend in front of an auditor. We update this card every release.

Lines of code600,142proprietary · self-hosted
Cognitive organs4049 capability layers
Swarm specializations18,751+20 ML families
Domain packs14live · production-ready
Pilot cohorts shipped3cohort 04 opens Jul 12
Engine runs to date2.4Macross pilots + production
Customers in production11mid-market across 6 verticals
Team22engineering · research · ops
// engineering dna

How a Godengine release is actually shaped.

Every component is constructed, not learned. Every release ships with the same nested anatomy. Here's what's inside the box.

One release ships with five nested modes wrapped around nine layers wrapped around four hundred and four organs.

We do not iterate at the organ level between releases — organs are stable, signed, versioned. We iterate at the composition level: which organs activate, in what order, under which constraint stack. That recipe is the moat. Everything else is open math.

L1Corearithmetic of cognition96 organs
L2Perceptionmultimodal intake38 organs
L3Temporalpast, present, projected44 organs
L4Domainvertical packs52 organs
L5Adversarialinternal red-team31 organs
L6Scale-bridgemicro ↔ macro28 organs
L7Memoryepisodic + semantic40 organs
L8Communicationexplainer + DAG36 organs
L9World-modelcoupled environment39 organs
// principles

What we will not compromise on.

Six principles that shape every architectural decision we make. We post these on the wall and we mean them.

P1

The recipe is the moat.

We will not open-source the convergence layer or the agent composition. The math libraries each organ uses are public; the composition is not. That is the moat.

P2

Self-hosted by default.

If a customer cannot run the engine inside their perimeter, we have failed. Every release ships a sealed container; every Tier 04 customer gets dual-key source escrow.

P3

Provenance is non-optional.

Every output carries the signed DAG of how it was produced. If we cannot sign it, we do not ship it. Regulators and internal audit see what the analyst sees.

P4

No model training on customer data.

We do not improve a shared model with your runs. Your calibration is yours; it lives on your infra; it is destroyed when you leave. The 404 organs are constructed, not learned.

P5

Mid-market first.

The decisions we care about are not the ones being made in three-letter consulting decks. They are the ones being made by capable, under-tooled teams in factories, hospitals, and treasuries. We sell to them first.

P6

No SI middlemen.

You talk to the team that wrote the code. There is no implementation partner, no reseller, no premium-tier-only direct line. Every customer gets a Slack channel with us.

// how we decide

The interior compass.

Three orientations that explain almost every decision we make — what we build, what we refuse, and what we keep open.

01

Engineered, not trained.

Every organ in the engine is a deterministic, math-first specialist. We don't fine-tune our way to correctness — we compose our way there. If the math doesn't exist, we don't ship the organ.

determinismcomposabilityno-RLHF
02

Audit before output.

Every Godengine run produces a signed DAG before the conclusion is exposed. The conclusion is never separable from the trace. If a regulator needs to follow the reasoning, they follow the same path the analyst saw.

signed-dagreplayableregulator-grade
03

Sovereign by default.

The engine runs inside your perimeter. Your data, your weights, your traces, your kill switch. We can't see your runs and we don't want to. Every customer is an isolated organism.

self-hostedair-gappablesource-escrow
// inside the building

Where the engine actually gets built.

A converted warehouse in Indiranagar, Bengaluru. 22 people, 14 whiteboards, two ranks of GPUs, one espresso machine that's been running since cohort 01.

// timeline

Three years, twelve inflection points.

Picked from the version-control log. Every entry is a moment after which the engine could do something it couldn't do the day before.

2023 · Q2
The thesisFirst sketch of the force-variable framework. A single Python file, eleven force aggregates, one Jupyter notebook. Two engineers, one whiteboard, one absurd idea.
thesis1 file2 people
2023 · Q3
Force aggregates → composable channelsThe eleven force aggregates collapse to seven and become first-class objects. The orchestrator gets its first pass-stack interface. Code base crosses 12,000 lines.
7 channelsorchestrator v0
2023 · Q4
96 organs · the Core layerLayer 1 reaches feature-complete. First non-trivial decision routed end-to-end with a signed trace. Forty agents, three hours, one cup of coffee that lasted longer than the run.
L1 complete96 organs
2024 · Q1
First convergence mathThe convergence layer ships in private — the math that decides which organ's output to trust when two organs disagree. Becomes the recipe we will refuse to open-source.
convergencethe-moat
2024 · Q2
First domain packFinancial Modeling & Risk ships internally. A capex pacing question that took a customer's analyst team two weeks gets answered in 47 seconds. The output is correct.
BFSI pack2wk → 47s
2024 · Q4
First paying customerA mid-market BFSI in Mumbai signs the first commercial Tier 02 contract. Self-hosted in their VPC inside three weeks. Engine still runs there today, build 1c2e.
first-customertier-02BKC
2025 · Q1
Layers 2-9 begin shippingPerception, Temporal, Domain, Adversarial, Scale-Bridge, Memory, Communication, World-Model. Each layer designed in isolation, integrated through the orchestrator pass-stack.
L2-L99-layer stack
2025 · Q2
Adversarial substrate · L5The Adversarial layer goes live. Every output is now pressure-tested by an internal red-team of 31 organs before exposure. Catches a counterparty exposure miscalculation in pre-prod.
red-team31 organs
2025 · Q3
v2.0 · 404-organ activationThe full nested-mode dispatch lands. Focused ⊂ Strategic ⊂ GOD ⊂ Titan ⊂ Omega. Omega-mode 30-tick runs verified for finite Ω and zero NaN/inf over 60-tick stability.
v2.0404 organs5 nested modes
2025 · Q4
First sovereign-tier deploymentA state-level dispatch decision pipeline goes air-gapped on customer-owned hardware. Dual-key source escrow signed. Engine runs without ever touching the public internet.
tier-04air-gapescrow
2026 · Q1
600K lines · cohort 01Codebase crosses 600,000 lines. First private-beta cohort onboards. 8 companies, 2-week PoCs, 7 conversions to Tier 02 or higher.
600K LOC7/8 conversion
2026 · Q2
v2.2 · 18,751 swarmsSwarm registry crosses 18,751 specializations across 20 ML families. Cyber and Insurance domain packs ship. Cohort 03 onboarding now. Cohort 04 opens July 12.
v2.218.7K swarmscohort 04
// footprint

Where the engine runs today.

Built in Bengaluru, deployed across India and the Gulf. Every node below is a live customer perimeter — the engine sits inside, not on top.

Built where the decisions are made.

Eleven production customers, four cohorts running, three sovereign deployments. The engine ships as a sealed container that runs inside the customer's perimeter — we provision, audit, and walk away. Every node is a live deployment, not a logo.

7 citieslive deployments
3 regionsindia · gulf · sea
11 orgsin production
0 SaaS tenantsself-hosted only

MAP · indicative · routes are deployment provenance, not data flow. The engine never phones home.

// team

Twenty-two engineers, researchers, and operators.

A small team by design. Every line of those 600K was written by someone you can talk to.

— Founder & CEO
Architect of the original thesis. The single Python file was his.
— CTO
Orchestrator and convergence layer. The composition recipe lives in his head.
— Head of Research
Adversarial and World-Model layers. Built the L5 red-team substrate.
— Head of Domains
Owns the 14 vertical packs. Designs new ones with customers in 4–6 weeks.
— Head of Infrastructure
Sealed-container builds. The reason every deployment looks identical.
— Head of Security
DAG signing, source escrow, audit pipelines. Sleeps with the keys.
— Head of Pilots
Two-week PoC playbook. Talks to every customer’s analyst team.
— Lead, Memory · L7
Episodic + semantic stores. The reason runs are replayable six months later.

+ 14 engineers across Perception, Temporal, World-Model, Communication, Ops, and field deployment.

// voices

What the people on the other side of the deployment say.

Customers, regulators, and a researcher we admire. Lightly edited; full transcripts available on request.

The first time we got a Godengine run with the signed DAG attached, our internal audit team had no follow-up questions. That had never happened before. We are still slightly suspicious.
Head of Internal AuditMid-market BFSI · Mumbai
We hired four firms before this. Three sold us a wrapper and a slide deck. The fourth sold us a dashboard. Godengine sold us the recipe, signed. It was the first proposal where the math actually closed.
CFOAuto-tier-1 supplier · Pune
The interesting thing isn't the 404 organs — it's that they refuse to ship one until the math is settled. It's the opposite of every AI roadmap I've reviewed this year. It's how avionics teams used to ship.
Independent ResearcherDecision-systems · cited 11K+
We needed to model surge, scheduling, ethics, and budget in one pass. The engine treated them as one problem. Six weeks later, no urgent case was deferred. Try getting any of our SIs to even define that as one problem.
COOHospital chain · Chennai
The engine never phoned home. We checked. Three different pen-test firms checked. It really doesn't phone home. That alone moved this from a 12-month procurement cycle to a 4-week one.
CISOState utility · western India
I joined because the codebase did the unglamorous thing well. Convergence math, sealed builds, signed traces. It's the first AI company I've worked at where the README isn't aspirational.
Senior EngineerJoined Q1 2026 · ex-trading systems
// in the press

A short selection.

We do not chase coverage. These are pieces that read the engine carefully and described it accurately, which is rare enough to list.

The Ken· Apr 2026

"A Bengaluru deep-tech outfit is quietly building the AI substrate Indian mid-market actually needs."

Read piece
FactorDaily· Mar 2026

"Inside Godengine’s refusal to ship a model — and what they ship instead."

Read piece
MIT Tech Rev. (IN)· Feb 2026

"Decision intelligence, but argued from first principles: a tour of the 9-layer stack."

Read piece
Forbes India· Jan 2026

"Self-hosted by design: the Indian AI company that won’t sell you a SaaS tenant."

Read piece
Mint Long Story· Dec 2025

"How 22 engineers in Indiranagar got the first sovereign-tier AI deployment in the country."

Read piece
a16z India Brief· Nov 2025

"Worth watching: a decision-intelligence stack that ships convergence math, not chatbots."

Read piece
CXOToday· Oct 2025

"Godengine’s 404-organ activation hits v2.0 in a quiet release that should not be quiet."

Read piece
YourStory· Aug 2025

"From single Python file to nine-layer cognition: a three-year build log."

Read piece
// invitation

Come see the engine running.

Bring a real question. Bring three data sources. We'll show you what 404 cognitive organs can do with it inside 48 hours — running on your hardware, signed at every step, leaving nothing behind.