Takelan Omnigate features

What you can use today, grouped by what it is for.

Tunnels

HTTP, HTTP/2, HTTP/3, WebSocket
TCP and UDP
File sharing
Hosted or private relays

Names and TLS

Custom domains
Automatic certificates
Reserved names

Protect

Traffic rules and WAF (WAF on paid plans)
Allow and deny lists, rate limits
Visitor sign-in: SSO, e-mail code, passcode
Passwords with schedules
Claim links, port knocking

Observe

Request inspector and replay
Live logs and traffic charts
Alerts: e-mail, webhook, Slack, Discord
Bandwidth caps and allowance

Teams and developers

Organizations
Audit log
REST API and MCP

Feature map: what you can use today, in five groups. Each group is described below.

Tunnels and protocols

HTTP tunnels over HTTP/1.1, HTTP/2 and HTTP/3, with WebSocket on all three.
Raw TCP and UDP tunnels.
File sharing: share a folder as a read-only site and download it with parallel, resumable transfers.
Takelan-hosted relays, regions and private relays you run yourself.
The real visitor address is passed to your app and cannot be forged.
Opt-in direct path and an opt-in cache (CDN) for static files.
Tunnels that expire: set a time to live and the tunnel is deleted at the deadline.

Security and access

Allow and deny lists by address, plus rate and connection limits per tunnel.
Visitor passwords with validity windows and weekly schedules.
Visitor sign-in in front of a tunnel: Takelan single sign-on, a one-time code sent by e-mail, or a shared passcode.
Claim links and port knocking for tunnels that should not be open to everyone.
Blocked ports: abusable public ports are blocked for everyone.
Two-step sign-in (TOTP) and a lockout after repeated failed sign-ins.
Visitor locations (IP geolocation) in the dashboard.
Refused visitors are counted per tunnel and day.

Traffic rules run in this fixed order on the edge. Access lists and plan limits come first, and visitor sign-in sits between the WAF and the request rules. The managed WAF is part of paid plans.

Observe and react

Request inspector: opt-in, short-lived capture of a tunnel's recent requests, with replay. Secrets in headers are redacted.
Live request logs, health checks and traffic charts.
Alerts to e-mail, webhook, Slack or Discord when a tunnel goes down or a plan allowance nears its limit.
A custom page for visitors when your tunnel is down.
Bandwidth tools: per-minute to per-year traffic, hourly caps and a monthly allowance.
Relay traffic by protocol and anomaly detection for relays.
Audit log with CSV and JSON export.

Names and domains

Reserve names under the platform domain.
Custom domains: serve a tunnel on your own host name with the DNS records the dashboard shows and automatic certificates.
Automatic DNS records for tunnels and relays.

Organizations and administration

Organizations: group accounts, child organizations and delegated management.
Audited "view as": an owner or administrator can see the dashboard as a member, time-limited and recorded in the audit log of both people.
Administrators manage users, plans, ports, relays and certificates.

For developers and AI agents

A REST API with interactive reference at /docs and the schema at /openapi.json.
Copy-and-paste examples in curl, Python and TypeScript (Dev Help).
A guide for AI agents at /ai.md, an index at /llms.txt and the full public text at /llms-full.txt.
A Model Context Protocol endpoint, read-only until the owner enables writes.

Not on this list means not available today. The plans page shows what is launching next.