Getting started with the ISPForge beta
A quick orientation so your first session goes smoothly.
1. What ISPForge is
ISPForge is a control plane for ISP networks. You describe your routing policy and peering vendor-neutrally - relationships (transit, peer, customer, internal), prefix filters from IRR, RPKI validation, communities, max-prefix limits, and ISPForge compiles it to the native syntax of each router platform you run, then deploys it through an agent that lives inside your network.
2. How a change reaches your routers
Every change is review-then-deploy: you make an edit, ISPForge shows you the exact per-router config diff, and nothing touches a live device until you approve it. An agent you install (Docker is the recommended path) holds the router credentials and applies the change over NETCONF / SSH / the RouterOS API.
3. Your first session
After you accept your invite and create your organisation, a good first path is:
- Set your ASN and AS-SET, and let ISPForge pull your PeeringDB record.
- Enrol an agent (Docker) and add one router.
- Build a policy profile, preview the rendered config, and deploy when it looks right.
The full walkthrough lives in the documentation.
4. This is a beta: what that means
- No SLA. Expect occasional downtime and breaking changes; we'll give notice where we can.
- Keep your own source of truth. Always review a rendered config before deploying it to production.
- Data may move. During the beta we may migrate or reset data as the product evolves.
- Your feedback shapes it. Tell us what's confusing or missing: that's the whole point of the beta.
5. Getting help & giving feedback
Reach us any time at beta@ispforge.com. Once you're in the portal, there's a Beta feedback link in the top bar for quick notes.