Live · paying customer
AnchoredIP
Public IPv4 addresses over WireGuard. An AI agent reaches a working tunnel in four calls with nobody in the loop. The proof that registry automation pays: it already does.
Registry & compliance automation
Your most repetitive compliance filing,
done by a machine — for a fixed price.
Poison-centre notifications across every member state. Safety data sheets re-issued when the rules change. Registry objects kept current. It is structured, high-volume, deadline-bound work — and almost none of it needs your expert's judgement to type. We automate that layer, so your people spend their hours where the judgement actually is.
One process. Fixed scope, fixed price. Your judgement stays yours — we take the mechanical work around it, never the decision.
If any of these is eating your week
- PCN, per country Re-keying the same mixture into the ECHA portal for every member state, chasing UFIs, redoing it on every reformulation.
- SDS on a rules change A new hazard class or an SVHC update, and a whole catalogue of safety data sheets has to be regenerated across languages.
- Registry objects Keeping the record — RIPE, or any registry — accurate as contacts, routes and ownership drift.
- Filing at volume Any authorised submission you make hundreds of times, where the format is strict and the judgement is already made.
That is exactly the shape we automate: a structured object, a validation ruleset, a submission portal.
How a pilot works
-
1
Pick one process
We take a single, narrow, repetitive filing — the one costing you the most hours — and nothing else. Fixed scope.
-
2
We build the pipeline
Plain-language request in, a validated object against the registry's own ruleset, a before/after diff your expert approves, then the submission. Fixed price.
-
3
You approve, it files
The decision stays with your specialist; the mechanical work disappears. If it doesn't save real hours, there is nothing to continue.
This isn't a promise — it's already running
Two systems online today, built on the exact pattern above. The first has a paying customer.
Live · 45,000+ pages
AnchoredRegistry
Sponsored LIR services and a directory that resolves any IP resource to its registry — built registrar-agnostic, RIPE first. One implementation, four doors: page, CLI, HTTP API, and an MCP server an assistant can call.
Reachable four ways, from one implementation
Whatever comes after the pilot — your team on a page, your systems on an API, your own AI agent through MCP — reaches the same code. Never a second path per door, so the same fact never gets to disagree with itself.
- PageA person acts in a browser.
- CLI
--jsonon every command, for scripts and pipelines. - HTTPA JSON API for any service to call.
- MCPAn AI agent uses the tool directly.
Tell us where your hours go.
One email. Name the recurring filing that costs your team the most time and needs the least judgement — we'll tell you within two working days whether we can automate it, and what a fixed-price pilot would cost.
Start a pilot — oleg@keepanchored.comNo sales call to book first. No credentials to hand over. Just the one question, answered.
Who you'd be working with
Keep Anchored is the studio behind the Anchored products, founded and run by Oleg Tropynin — a software engineer working independently since 2010, building registry, networking, and compliance automation end to end: the edge, the API, the agent interface, and the page.
The way of working is the same in every project: the smallest system that is actually complete, standard tools over dependencies that rot, and a plain proof that each piece works — the command you would type and what it printed. For regulated work that means the expert's judgement stays with the expert; the machine takes the mechanical work around it, and never the decision.