​
What is kurnl?

kurnl is an open access internet platform. It manages shared network infrastructure — switches, buildings, and subscriber ports — and provides a multi-ISP marketplace where subscribers choose and sign up for internet service. As a provider (ISP), you list your plans on the kurnl marketplace, manage your subscribers, and connect your checkout or back-office system to kurnl’s provisioning layer via API.
New here? Start with the Partner Integration Overview — it explains the model (no plugin to install), the three things you build, and which integration path fits you.

​
What you can build

External Checkout (CKO-03)

Subscriber picks your plan on the kurnl marketplace, completes payment on your own checkout page, and you call one API endpoint. kurnl handles subscriber creation, subscription, and port provisioning.

Provider-Initiated (CKO-04)

Provision subscribers directly from your own system — no Stripe, no marketplace redirect. One API call creates the subscriber, subscription, and activates the port.

Subscriber Management

What the partner API does and doesn’t manage: suspend/restore when you own billing, plan change, subscriber self-service endpoints, and where the dashboard still takes over (activate, cancel).

Bulk Provisioning

Provision up to 100 subscribers in a single batch call. Poll for batch status and handle partial failures gracefully.

​
How the platform works

kurnl sits between the physical network and your subscriber-facing system. When a subscriber signs up, kurnl:
  1. Creates a subscriber record and subscription in the database
  2. Looks up the switch port assigned to that subscriber’s location
  3. Configures the port via SSH — sets the VLAN, applies bandwidth limits, and optionally binds the subscriber’s MAC address
  4. Fires webhook events to your system at each stage
You never need to touch the network layer directly. kurnl handles all switch communication.

​
Authentication

kurnl uses two authentication mechanisms depending on the integration type: Your API key lives on the API Key page (/api-keys); the shared webhook secret on the Checkout page (/checkout-settings).
The sandbox has its own webhook secret (from GET /sandbox/provider-info) but no sandbox API key — API-key endpoints always act on your live account. See Sandbox Setup.