The ops console ships with the platform.
Administration, identity, real-time notifications, and full change history are included. Day two is not a services engagement.
- ·The admin console ships with the platform: users, tenants, roles, permissions, sessions, queues, connectors, and logs. Day two is not a services engagement.
- ·Sessions are server side, so a contractor's access can be revoked instantly across every tenant they belonged to.
- ·Change history is recorded by the database engine, so who changed what and whether they were allowed to is answered from data rather than archaeology.
Platforms get bought for features and abandoned over operations.
The demo shows the product. It doesn't show who manages users, roles, sessions, queues, and failures at 7am, or with what tooling. Too often the answer is a services contract and a pile of custom admin screens.
Compliance has the same gap. Who changed what, when, and could they? If the platform can't answer uniformly, every audit becomes archaeology.
The mechanisms, not the adjectives.
A complete admin client
A workspace-style web console with docked multi-tab editing, searchable grids, and modules for users, tenants, roles, permissions, sessions, queues, connectors, validation rules, and system logs. New governed tables get management screens driven by the same registry the API uses. A desktop build is available for restricted networks.
The admin surface scales with the registry, not with a backlog of bespoke screens.
Identity done conservatively
Argon2id password hashing, server-side revocable sessions with sliding timeout, OAuth and OIDC single sign-on, brute-force lockout with login throttling, and a full audit of login attempts. Users are global; tenant membership is many-to-many with per-membership roles, and multi-membership users pick a tenant at login.
Instant revocation and a record of who acted as which tenant. Stateless tokens can't give you either.
Notifications on a transactional outbox
Per-user, tenant-scoped notifications deliver over SignalR within seconds: bell, unread badge, searchable history. Offline users catch up on connect. A task tracker shows long-running work like report runs with full request and response trails.
The people responsible find out when something fails, instead of finding out when someone asks.
History at the engine level
Governed tables are system-versioned with SQL Server temporal tables, so point-in-time reconstruction is built in. A transaction log with correlation IDs groups multi-table saves, and standard audit columns with soft delete run throughout.
Change history that an application bug can't skip, because the database engine records it.
A security review, answered from the console.
- 1
Who can see this table? The permission registry answers per role, per tenant, with no code to read.
- 2
Who touched this record this quarter? Temporal history reconstructs it point in time.
- 3
Terminate this contractor's access now. Server-side sessions revoke instantly, across every membership.
- 4
What failed last night? System logs and notifications show the queue batch, the retries, and the outcome.
- 5
Prove it. Export the logs and the audit trail. It's all data.
The AI angle.
Deloitte found only 21 percent of companies have mature AI-agent governance while three quarters plan to deploy agents. Agents on Forge are sessions: visible in the console, revocable instantly, with their actions in the same audit trail as everyone else's. Governing agents with the same tools that govern people is the manageable version of that future.
Keep going.
Security & multi-tenancy
Tenant isolation derived from foreign keys and enforced in one data path. No filter to forget.
Go deeper →Collaboration
Google-Docs-style co-editing over multi-table enterprise data, committed in one transaction.
Go deeper →Integration & automation
Background automation that obeys the same tenant boundaries as interactive users.
Go deeper →See it on your schema, not ours.
A fixed-price assessment gets this running over your actual data.