One cloud. Five layers.

Bring your whole stack to life here.

From the address your users hit down to the data your app sits on — assemble it here, pay by the minute for what actually runs. We'll spot you 20 credits. No card, no call. Spin something up and see whether we're any good.

Claim 20 Credits Explore the Cloud
THE CATALOG

Everything We Run

Five layers you stack into your own — the outward-facing edge on top, your application's data core at the bottom. Open a layer to see what's in it.

  • Rent IPv4A dedicated IPv4 address as your fixed entry point.
  • Rent IPv6A dedicated IPv6 address.
  • L3 — Forwarding and FirewallForwarding by IP and port, with packet filtering at the network layer.
  • L7 — Application-level network controlOur layer-7 router: routing, access, rate limiting, and protection.
Open the Network layer
  • Binary (aarch64)A compiled binary built for the aarch64 architecture.
  • Node.jsA Node.js project, uploaded as its source.
Open the Executable layer
  • RunStart an Executable; DRP wraps it in a container with the right environment.
  • Isolated LinuxA small isolated Linux instance that's yours to work in.
Open the DRP layer
  • ValkeyOpen-source in-memory store: cache, sessions, queues, rate-limit counters.
Open the In-memory layer
  • Apache AGEGraph queries (openCypher) inside the same database.
  • ParadeDBFull-text search and analytics directly in Postgres.
  • pgvectorVector storage and similarity search for embeddings.
  • PostgreSQLThe relational core the three extensions run on.
Open the Database layer

PostgreSQL, Apache AGE, ParadeDB, pgvector, and Valkey are trademarks or marks of their respective owners. Punkolink provides managed hosting of these open-source projects and is not affiliated with or endorsed by them.

Try It Out Full Details
ROUTING CONSOLE

See L7 In Action

One readable row per route — method, path, target, and access, all in one place. No nested config blocks to reverse-engineer.

Routes
L7 routing table — method, path, type and access.
Interface preview — a look at the L7 console, not a live instance.
Method Path Type Access Require Auth Actions
Everything it does

Load balancing

Distributes traffic across backends so no single node carries it all.

Rate limiting

Caps request rates to keep abuse and spikes from overwhelming backends.

Bot protection

Filters automated bot traffic away from your services.

Layer-7 access control

Per-route, role-based access rules at the application layer.

Redundancy

Failover across servers so the loss of one doesn't take the service down.

Brute-force protection

Blocks repeated credential-guessing attempts.

Availability monitoring

Continuous health checks on the resources the router forwards to.

Layer-3 access control

IP-based filtering with allow and deny lists.

Graphical challenge

A CAPTCHA-style check to separate humans from automated traffic.

Status reporting

Automated reports on the state of your routed resources.

Static file storage

Serve static assets straight from the router.

Web GUI

A browser admin panel for managing the router without the command line.

More on the Network layer

From The Field Notes

View All Posts →
Concept

A Gigabyte for Fifty Megabytes

Data centers are more expensive than ever before — and it's not just about the money. How much of that rented capacity is actually doing useful work?

Sep 8, 2026 · 7 min read
Business

I Spent Years Being the 3 A.M. Call for Companies That Couldn’t Fix Their Own Networks

It’s a situation familiar to many system administrators. It’s noon, the busiest part of the workday — and everything has gone down.

Jul 1, 2026 · 6 min read

Join Us

Create an account, claim 20 free credits, and provision your first layer.

Join Us