Files
ZitPlane/docs/FEATURES-STATUS.md
T

2.0 KiB

ZitPlane — Actual feature availability / limitations

Snapshot: 2026-11-22, P05-CI-01 source preparation based on baseline 7ecf531. SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION.

Feature Source present CI/build verified Live/deployed
Official ZITADEL Go backend image configuration Yes, P02 No No
Local PostgreSQL and loopback Traefik stack Yes, P02 No No
Official prebuilt Login V2 service in local Compose Yes, P02 configuration No No
Official Login V2 customisable source Yes, P03 v4.20.4 No No
Login V2 signup/password/OTP/MFA/passkey/IDP source routes Present upstream No No
Custom Account Portal Next.js app Yes, P04 No No
Portal login OIDC and Auth.js callbacks Yes, P04 source No No
Portal Overview / Profile / Security pages Yes, P04 No No
Read-only GET /api/account/me Yes, P04 No No
Password/MFA/passkey changes inside Account Portal No N/A No
Mutable profile editing / device sessions / identity deletion No N/A No
Global ZITADEL SSO logout No N/A No
Subscriptions, payments and SaaS billing Outside ZitPlane scope N/A No
Gitea Actions CI verification workflow P05 source added, manual dispatch Not yet verified Not deployed
Gitea Actions CI and isolated integration tests Verification scripts prepared; full OIDC E2E absent Pending No
Coolify production stack, TLS, routing and backups No No No
Public auth.vib.tools/login URL Proposed only No No
Public account.vib.tools account website Proposed only No No

Prior historical P02 source-only Python static tests passed 3/3 in earlier work, and P03 upstream imported Git blobs matched 638/638. These are not equivalent to a running authentication system.

Future feature additions need an evidence-backed status update here, an exact developer implementation record in project/, a pre-change scope entry in notes/, and corresponding user guide updates.