ahel is Estonian for chain.

The model was never the bottleneck. What keeps AI from doing real work is everything around it: the context, the integrations, the credentials, wired differently on every project, by hand, again. ahel is that setup, defined once and served to every agent through one link.

The stance behind it: your gateway is yours. You decide what goes in it, your credentials open only where you said they could, and switching agents never means starting over.

You store your setup in ahel once: the skills you rely on, the MCP servers you run, the credentials you pay for. Any MCP-capable agent (Claude Code, Codex, Cursor) reads that stack through one link, so a new machine or a new tool starts configured instead of empty.

The part most tools skip: the keys. Credentials sit sealed and encrypted, masked in the UI, every decrypt logged. Agents connect through OAuth, so no key ever lands in a client config.

ahel.ai is where your gateway lives, and team gateways are next, so onboarding a teammate will be sending one link. Signup is open and free: sign in to start, or see pricing. Ahel is free right now, on your own keys.

Every AI tool ships its own config format, its own key storage, and its own idea of setup, and developers pay for that fragmentation one evening at a time. The direction we’re building toward is a stack that outlives any single tool: stored once, versioned, shared with a team, and readable by whatever client ships next. The gateway is where that starts.

We host in the European Union and encrypt the credentials you store. The full picture, mechanism by mechanism, including a plain list of what does not exist yet, is on the security page. For anything else, the contact page reaches a person.