01
Secure by default.
Authorization code with PKCE is the interactive path. The implicit and hybrid flows are off unless an operator widens the setting, and so is anonymous client registration.
Pre-release. NCode Identity is under active development and is not ready for production use.
NCode Identity is an OpenID Connect and OAuth 2.x provider for .NET, with a management console. The hosted platform runs only the published artifacts it offers self-hosters, so both run the same thing.
Sign-up for the hosted platform opens [date]. Until then the source, the decisions and the open issues are public.
01
Authorization code with PKCE is the interactive path. The implicit and hybrid flows are off unless an operator widens the setting, and so is anonymous client registration.
02
Platform, team, tenant, resource-server and client settings merge by declared rules. A tenant cannot configure its way out of a platform or team security decision.
03
Access tokens can be sender-constrained with DPoP or mutual TLS. A FAPI 2.0 security profile tightens every setting it governs in one move.
04
Every stored secret is encrypted under a root key held in AWS KMS, Azure Key Vault or Google Cloud KMS. Each tenant has its own master key, so deleting a tenant crypto-shreds its data.
The code a self-hoster could use is public, and so is the infrastructure code of the hosted platform. The managed offering keeps private only its own parts: billing and metering, sign-up, the customer portal, support tooling and private runbooks.
| What is compared | Self-hosted You run it, on your infrastructure. | Hosted NCode runs it, at ncodeid.net. |
|---|---|---|
| What runs | The packages, the host and console images, and the host chart. A host takes the layers it needs and replaces the rest through public contracts. | Only the published artifacts the platform offers self-hosters. |
| Source | Public, under Apache-2.0. | The same source, and the platform's infrastructure code, also public. Its security does not depend on hiding how it is built. |
| Your environments | As many deployments as you choose to run. | Tenants on the production platform. Your development, test and staging are tenants too. |
| Root key for secrets | Yours, in AWS KMS, Azure Key Vault or Google Cloud KMS. | [who holds the root key] |
| Operations | Yours: upgrades, backups, monitoring. | NCode's. Infrastructure changes are planned on a pull request and applied after review. |
| Price | No license fee. | [price] |
| Limits | Your own settings. | [tenants, users and requests per plan] |
| Availability and support | Yours to keep running. Known work is tracked in public issues. | [availability target] [support terms] |
A tenant holds its own clients, keys and settings. Create one on the hosted platform when sign-up opens [date], or run the reference server on your own machine today.