Opyntel

One monitoring dashboard
for your apps, front ends and servers.

Apps on Railway, Render and Fly.io. Front ends on Vercel and Cloudflare. Servers on Hetzner, Hostinger VPS or any Linux box. Status, CPU, memory, deploys and spend side by side in one monitoring dashboard, worst first.

See how it works
Integrations

One place for every platform you run on

Your apps, front ends, self-hosted PaaS and servers report into one Opyntel workspace. Connect each with a read-only API token, or install the small Opyntel agent on your servers.

Opyntel works with

Don’t see your platform? From your Opyntel account you can request an integration with more platforms. Until then, and tell us which one you run on.

One dashboard

Many dashboards, or just one

Every platform in your stack brings its own dashboard, and every service in them is another click. Opyntel puts them all in one monitoring dashboard, down and degraded first.

Opyntel

Today: 5 dashboards

  • Railway

    App platforms

  • Vercel

    Front-end and edge

  • Cloudflare

    Front-end and edge

  • Hetzner

    VPS and servers

  • Coolify

    Self-hosted PaaS

Services

Down and degraded first

Example data
Services
6
Down or degraded
2
Monthly spend (estimated)
$38.20
Last sync
40 s ago
ServiceStatusProjectSourceCPURAMLast deploy
workerdownshopRailway——2 h ago
apidegradedshopCoolify0.61 vCPU412 MB18 min ago
webdeployingshopRailway0.05 vCPU180 MBjust now
postgresokshopCoolify0.22 vCPU1.1 GB6 d ago
redisokshopCoolify0.03 vCPU64 MB6 d ago
cronstoppedtoolsRailway——3 d ago
How it works

From token to one dashboard in four steps

Go from token to every service in under five minutes, with every platform in one dashboard and Opyntel telling you when something changes.

Read-only. One dashboard. Told when it changes.
See all features
Read-only by design

Handing over a token? It can only read.

You should not have to trust a third party with write access to your platforms. Opyntel asks for a read-only token, and its own code only ever sends read requests.

  • Connectors reach the network through a single read-only transport that only offers GraphQL queries, GET and HEAD.
  • GraphQL documents are parsed before sending: mutations and subscriptions are rejected before any request is made.
  • Every outgoing request is checked again and must go to the platform’s own host, so a token never reaches anywhere else.
  • A test fails if any connector imports its own HTTP client, so the transport cannot be bypassed.
  • Some platforms start deploys and restarts through GET requests, which the transport allows: Opyntel asks for a read-only token so the platform itself refuses those actions.
What the transport lets through

Illustration of the checks, not live traffic

  • query { projects { … } }sent
  • GET /api/v1/applicationssent
  • mutation { serviceDelete }not a query
  • DELETE /api/v1/applications/…write method
  • GET https://elsewhere.exampleother host
FAQ

Questions, answered

What Opyntel connects to, what it needs from you and what it will never do.

App platforms: Railway, Render, Fly.io, Heroku, DigitalOcean App Platform, Northflank and Koyeb. Front-end and edge: Vercel, Netlify and Cloudflare. Self-hosted PaaS: Coolify, Dokploy and CapRover. VPS and servers: Hetzner, DigitalOcean Droplets, Hostinger VPS, Linode (Akamai), Vultr, Scaleway, OVHcloud and any Linux server through the Opyntel agent.

and tell us which one you run on. From your Opyntel account you can then request an integration with more platforms, and those requests decide what we connect next.

No. Connect a read-only token and Opyntel finds your services. The optional agent is only for your own Linux servers.

Keep them for outside-in checks and for your own servers. Opyntel covers the services on platforms where you cannot put an agent, shows deploys and crashes beside the metrics, and tracks spend.

No. Opyntel is the screen you check first. It tells you what is down and what changed, then you go to your logs.

No. Every connector request goes through a read-only transport: GraphQL queries only, GET and HEAD for REST APIs, and only to the platform’s own host. Anything else is rejected before it is sent. Some platforms start deploys and restarts through GET requests the transport lets through, so Opyntel asks for a read-only token: with that scope, the platform itself refuses to act on them.

An API token for your platform with read access. Some platforms need an extra read permission for detailed host metrics; without it, states and events still work.

Metrics refresh every hour on Free, every 15 minutes on Pro and every 5 minutes on Enterprise. History is kept for 30 days on Free, a year on Pro and without a limit on Enterprise.

Free up to 10 services. Pro is $19 a month and Enterprise is $49 a month, with two months free on annual billing. Founding members from the waitlist keep Enterprise free for life. See Opyntel pricing and plans.

It is not available yet. Join the waitlist and we’ll email you when your access is ready.

The alerts your platform doesn’t send.

One dashboard for everything you run, with the alerts your platforms leave out. Read-only, nothing to install in your apps.

See how it works