Get connected

How do you want to reach us?

There are four ways in. They are not tiers and they are not products, they are just doorways. Most people end up using more than one.

Your agents

Give an agent a private path to something, without putting that something on the internet.

A tool interface your assistant calls directly
SDKs for TypeScript and Python
Private routes to your own services, never publicly exposed
Shared context between agents, wherever they run

Best if you are building with models and they need to reach real systems.

Your code

Point an application at us and let the edge do the rest.

A REST API with an OpenAPI description
Routing, caching, compression and a firewall as policy, not as products
Certificates that renew themselves
Per request visibility, so a slow page has an answer

Best if you ship software and want it fast and protected everywhere.

Your servers

Put us in front of what you already run, wherever it runs.

Any cloud, any colocation, your own metal, or all three at once
Health checks and failover across providers, not just within one
Traffic split by path, method, country or network
No requirement to move anything first

Best if you already have infrastructure and want it to behave as one thing.

Your network

Join at the network layer, the way networks have always joined.

Overlay or tunnel
Physical cross connect
A BGP session, and bring your own addresses
Peer with us directly

Best if you run a network yourself and would rather talk in prefixes than APIs.

Then it is probably more than one

Not sure which one?

Then it is probably more than one, and that is the usual answer. The point of putting them on the same platform is that you do not have to decide up front, or sign a separate contract each time you change your mind.

Tell us what you are building and we will tell you which door is the short one.

We are taking a small number of people first.

A person sets up each one, and there are about thirty of us.

Ask for a key