# ZFORGE: a self-hosted Zero Trust dashboard for SMEs, built on OpenZiti 2.0

**URL:** <https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190>\
**Category:** Ziti Overlay\
**Created:** [October 19, 2026, 5:43pm UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190 "2026-10-19T17:43:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anake-an](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/anake-an/32/4396_2.png) [@anake-an](https://openziti.discourse.group/u/anake-an)\
**Post date:** [October 19, 2026, 5:43pm UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190/1 "2026-10-19T17:43:00Z")

</div>

Hi everyone. I'm Aniq, a Network Engineering student at Universiti Malaysia Sabah. For my final year project I built ZFORGE, a management dashboard that puts OpenZiti in the hands of a small IT team.

**Why:** small businesses here mostly use MAC address binding or a flat VPN. MAC randomisation breaks the first, and the second gives every signed-in device the whole network. OpenZiti solves both, but the CLI and policy model are a lot for a one-person IT team.

**What it does**

- Device identities with a guided enrolment flow and emailed setup links
- Apps, access rules, posture checks and location rules, all point-and-click
- Live sessions with an end-session action
- Service cloaking checks, so office apps keep zero open inbound ports
- A hash-chained audit log, grouped security incidents and push alerts

**Architecture:** a Next.js dashboard and a Laravel API proxy in front of an OpenZiti 2.0.0 controller on AWS EC2. Office connectors are private routers in Docker, on the same Docker networks as the apps, so nothing on the office server is exposed. A port scan of the office VM shows nothing but the management link.

**Something I'd love feedback on:** with OIDC/JWT clients there are no API or edge sessions, so I build live sessions from `/fabric/v1/circuits` (using `tags.clientId` and `tags.serviceId`). Ending a session deletes the identity's circuits and calls `POST /edge/management/v1/revocations` with type `IDENTITY`. Is that the approach you'd recommend, or is there a better signal for "this device is connected"?

Launch video: [https://youtu.be/gjXBzeBfLrI?si=HH\_jWVRJxXpt2uK0](https://youtu.be/gjXBzeBfLrI?si=HH_jWVRJxXpt2uK0)  
Live site: [https://zforge.my](https://zforge.my)  
LinkedIn: [www.linkedin.com/in/aniqsfd](http://www.linkedin.com/in/aniqsfd)

Thanks to the OpenZiti team and community. Happy to answer any questions.

 ![Screenshot 2026-10-19 191934](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/6/6184b70985a953625170dfae9dcc6c33ef2d901f.jpeg)

 ![Screenshot 2026-10-19 192250](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/a/ac1a9b33da8df5fce1ea8cc123b6c711a29075f0.png)

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [October 21, 2026, 12:08pm UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190/2 "2026-10-21T12:08:11Z")

</div>

Hi @anake-an, welcome to the community and to OpenZiti and thanks for sharing your project!

> [@anake-an](#):
>
> Is that the approach you'd recommend, or is there a better signal for "this device is connected"?

Generally, I think we have been using the identity's 'edgeRouterConnectionStatus" for example:

```auto
ziti edge list identities 'name="clint"' -j | jq .data[].edgeRouterConnectionStatus
"online"

```

---

<div class="post-metadata">

**Author:** ![anake-an](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/anake-an/32/4396_2.png) [@anake-an](https://openziti.discourse.group/u/anake-an)\
**Post date:** [October 23, 2026, 1:30am UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190/3 "2026-10-23T01:30:35Z")

</div>

Thanks, that’s really helpful. ZFORGE was reading `hasEdgeRouterConnection`, which I now see also counts router heartbeats in the default hybrid mode. I’ll switch the online indicator to `edgeRouterConnectionStatus` and keep circuits only for showing which app a device is using.

For ending a session, is deleting the identity’s circuits plus an `IDENTITY` revocation still the right approach for OIDC clients, or is there a cleaner way to drop a client’s router connection?

---

<div class="post-metadata">

**Author:** ![dmuensterer](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dmuensterer/32/2451_2.png) [@dmuensterer](https://openziti.discourse.group/u/dmuensterer)\
**Post date:** [November 15, 2026, 6:08am UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190/4 "2026-11-15T06:08:12Z")

</div>

How does this compare to Ziti Admin Console?

---

<div class="post-metadata">

**Author:** ![anake-an](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/anake-an/32/4396_2.png) [@anake-an](https://openziti.discourse.group/u/anake-an)\
**Post date:** [November 17, 2026, 2:14am UTC](https://openziti.discourse.group/t/zforge-a-self-hosted-zero-trust-dashboard-for-smes-built-on-openziti-2-0/6190/5 "2026-11-17T02:14:37Z")

</div>

Hey, thanks for checking it out!

They both talk to the same controller, just for different people. ZAC gives you the full OpenZiti model, so you set up services, configs and each policy type yourself. That's great if you already know how it all fits together.

ZFORGE is more for a small IT team that doesn't have time to learn all that. For example, one access rule sets up the service policy, service edge router policy and edge router policy for you. It also adds some extras like email setup links for devices, location rules, port scans to check apps stay hidden, and an audit log with alerts.

It doesn't do everything though. Things like auth policies and JWT signers are still a ZAC or CLI job. So if you know Ziti well, ZAC is probably the quicker tool. ZFORGE is for the admin who just wants it to work.

PS: still curious if deleting the circuits plus an IDENTITY revocation is the right way to end a session for OIDC clients. Any tips welcome!
