OPTETRON

Founder availability

The founder is currently under an exclusive contract and cannot accept new requests. You can still subscribe to our newsletter or email us directly at contact@optetron.com.

Local-first AI agents.
You own the code.

We design and build multi-agent workflows that run inside your infrastructure. The engine is configurable, the source code is yours, and your data never leaves your network.

▞SYS.01two wrong defaults
The problem

Two ways to get AI inside your company. Both are wrong.

You either rent a SaaS that ships your data abroad on every call, or you hire an AI engineer at €100K and wait nine months for a working prototype. Neither survives a real audit. Neither scales past the pilot.

SAAS COPILOTS
€18 — 60K / yr
subsidized · prices climbing
  • ✕ Your prompts and documents leave your network on every call.
  • ✕ APIs deprecate, models change, prices triple — without your consent.
  • ✕ Cloud Act, T&Cs drift, training-data leakage. You don't own the surface.
  • ✕ You can't fork it. You can't audit it. You can't keep running it.
IN-HOUSE AI ENGINEER
€80 — 120K / yr
+ 9-month ramp · retention risk
  • ✕ Half a year before they ship anything that survives prod.
  • ✕ One person away from "we have to start over".
  • ✕ Every junior team rebuilds the same orchestrator from scratch.
  • ✕ No published track record on the multi-agent stack.
OPTETRON
€-K / project · scoped
battle-tested engine · keep the code
  • ✓ A multi-agent engine that already works — orchestrator, memory, tools, eval loop.
  • ✓ Deployed on your infrastructure. Source code in your private remote.
  • ✓ Open-source models by default. Frontier APIs only when you decide.
  • ✓ Audit logs, permission boundaries, a rehearsed stop procedure. Designed to be inspected.
▞SYS.02a stack you can fork
The engine

One engine. Many configurations.

One codebase underneath: orchestrator, agent runtime, memory, tools, evaluation loop. It ships in three shapes. Local agents that auto-evolve, tuning themselves on your real traffic. Chatbots that answer your customers on your own documents. Optimization loops that sharpen a system you already run. Your data stays inside your boundary unless you wire in a frontier API.

L4 — INTERFACE
Configuration
three products · your graph
Your AI employees
auto-evolve · on your infra
Talks to your customers
grounded · your data
Tunes what you run
always-on
Custom graph
your spec
L3 — ORCHESTRATION
Agent runtime
front · knowledge · service
Front Agent
routing · intent
Knowledge Agent
RAG · grounding
Service Agents
tool calls · DB · APIs
Eval loop
deterministic checks
L2 — STATE
Memory & tools
scoped · auditable
Vector store
qdrant · pgvector
Episodic memory
scoped · revocable
Tool registry
your APIs · your DBs
Audit log
every call recorded
L1 — INFERENCE
Models
open by default
Llama 3.3
70B · q4 · q8
Mistral · Mixtral
8x7B · 8x22B
Qwen 2.5
72B · code · vision
Frontier API
on demand · your keys
▞SYS.03the four non-negotiables
Doctrine

Three things we refuse to compromise.

Every page, every conversation, every line of code reinforces these. They're not features. They're the floor.

[ 01 ]

Privacy

Every byte stays on your hardware. Prompts, documents, vectors, logs — none of it crosses the boundary you set. Air-gap compatible. Audit-ready by default.

zero egress · GDPR · sovereign
[ 02 ]

Ownership

You receive the source code. It lives in your private git remote. You can fork, audit, extend, and keep running it if Optetron disappears. No subscription holds it hostage.

source · git · perpetual
[ 03 ]

Control

You choose the models, the hardware, the integrations. Open weights by default, frontier APIs only when you decide. Permission boundaries on every tool. A stop procedure your team has rehearsed.

open weights · your choice
▞SYS.04days, not quarters
Deploy

It's software. It deploys in days.

Optetron isn't a quarter-long build — the engine already exists. Install it on your infrastructure, connect your data and tools, and it's live. The source sits in your private remote from the first day, and nothing runs anywhere but your hardware.

1

Install

Drop the engine onto your infrastructure — on-prem, your VPC, or air-gapped. No SaaS account, no data leaving your network.

your infra · day one
2

Connect

Point it at your problem: your data, your tools, your models wired in. The engine is configurable, not bespoke — the graph already works.

your data · your tools
3

Live

It answers on your real traffic in days. The source code is in your private git remote from the start — yours to fork, audit, and keep running.

days · yours to keep

Prefer we handle the integration for you? That's optional — a scoped setup or an ongoing retainer. See consulting →

▞SYS.05it improves itself
Auto-evolve

Most software peaks the day you deploy it. This one doesn't have to.

To improve, ordinary software needs the vendor back in the loop — a new contract, a round-trip to their cloud, your data in their hands again. The engine you own works the other way.

Optetron auto-evolves. After deployment, the engine can keep optimizing its own behavior from your real traffic — on your hardware, inside your boundary. No vendor round-trips, no re-engagement fee. The capability to improve stays on your side of the line, not the vendor's.

Sovereignty intact. Nothing leaves the perimeter. You own the code — and any improvement stays inside it.

  • Deploythe engine goes live on your infrastructure
  • Real trafficyour users, your data — never leaving your boundary
  • Auto-evolvethe engine can tune its own behavior on your hardware
  • Better responsesresults feed back into the loop — on your side
[SYS.06 — TALK]

Tell us where the data can't leave.
We'll bring the agents to it.

Scoping calls are paused while we're at capacity. Subscribe to the newsletter and you'll be the first to know when they reopen.