FactoryTechnology
Your stack stays. Nothing is migrated.
We read what you already run. Eight layers, all deployed inside your environment. The ninth, the Factory that builds them, stays with us and never ships.
We write connectors continuously, as MCP servers and as direct API adapters, and the library grows with every engagement. Anything reachable through a spec, a database or a file is already in scope. Anything that is not gets built for you during delivery.
183 connectors, and the number goes up on every project.
We build connectors as a habit, not as a project. Most are MCP servers, which means a play can reach a system through one stable interface regardless of what sits behind it. The rest are direct API adapters where a vendor gives us something better to work with, plus database reads, file drops and portal readers for systems that offer nothing at all.
Seventeen need no credential, because they read the public record. Those are the ones that let us run something real in a first meeting, before you have given us anything.
When your stack includes something we have not read before, we write it during delivery. It joins the library, and the next company running that system gets a faster build because of you.
One stable interface per system, versioned, reusable across every client that runs it.
Where a vendor's API is richer than any wrapper, we use it and keep the mapping.
Direct reads of anything already modelled, plus CSV, Excel, SFTP and email drops.
A custom connector built by the deployed engineer, in days rather than a procurement cycle.
Sequencing matters more than coverage. Public record and a single file export cover the first meeting and usually the pilot. A real connector is written during delivery, so integration is never what delays a decision.
Eight layers in your environment. One that stays with us.
| Layer | What sits here | Whose it is |
|---|---|---|
| Systems of record | SAP, Oracle, Tally, Salesforce, your service app, dealer portal, agency management system, PMS or hospital system. We do not touch, replace or migrate them. | Yours, untouched |
| Capture and connectors | MCP servers and API adapters, plus SQL, SFTP, webhook, email drop and file upload, and public sources that need no credential. | Built from our library, runs in your environment |
| Context graph | Golden records for account, quote, unit, contact, dealer and enquiry, resolved across systems, versioned, with lineage on every field. | Yours on handover |
| Case memory | Bounded episodes with their circumstances attached, anchored to resolved entities, including what never reached a system. | Yours on handover |
| Patterns and confidence | Claims formed across cases, each with evidence, an owner, a half-life and a confidence that decays. Stale claims are held out of decisions. | Yours on handover |
| Definitions | What open pipeline, stalled quote and dealer coverage actually mean, with owners and exclusions. A change is a release, not an edit. | Yours on handover |
| Plays and orchestration | The catalogue running against your memory, with spans, cost and token accounting on every run. | Yours on handover |
| Write-back and approvals | Nothing enters your systems without a named approver. Dry run first, audit trail, rollback window. | Yours on handover |
| The Factory | Connector library, resolution engine, build patterns, evaluation harness, model routing. Never shipped, never licensed. | Ours, permanently |
One definition of every entity, built once, then read by every play.
A machine tool builder we scoped had a customer called Meridian Fasteners. SAP knew them as MERIDIAN FASTENERS PVT LTD. The CRM had Meridian Fastners, a typo from 2019 nobody ever fixed. The dealer portal had M/s Meridian. The service app filed them under the plant address in Rajkot, with no company name at all.
So four systems held four customers. Sales saw an account that had not ordered in two years. Service saw fourteen machines under contract and kept visiting. Finance saw a receivable. Nobody saw that the same company had let an AMC lapse, taken a competitor's quote, and was about to replace eleven machines.
Resolution is what makes those four rows one company, and one company is what makes a case history possible. Without it there is no memory, only records.
Configuration, not architecture.
408 models across 51 providers. Extraction, reasoning, speech and embedding route separately, and any of them can be swapped without touching the play, so a price change or a deprecation is a config edit rather than a rebuild.
A frontier model pinned to an in-region endpoint, a sovereign provider, or open weights running inside your own VPC with nothing leaving your territory. Air gapped is possible.
A claim whose source cannot be resolved is dropped before it reaches you. That is a gate in the evaluation suite, not an instruction in a prompt, so it cannot regress without a code change.
No client data trains any model. PII is masked at extraction and contact details tokenised. Sign-in through your identity provider, run logs retained on your schedule.
Lowering a threshold is a decision, not a setting. It is versioned, it has a named owner, and it appears in your quarterly review. Nobody quietly moves a gate to make a release pass.