About IdentitySuite

Who builds it, why it exists, and what you can count on.

Who is behind IdentitySuite

IdentitySuite is designed, built and maintained by Stefano Pinato, a .NET developer based in Italy. There is no marketing department behind this site: the person who writes the code is the person who answers your emails.

My background is in Microsoft systems administration: I worked as a sysadmin and then as IT manager for a company in the food industry. Programming stayed a parallel interest for most of those years — it became my main line of work in 2018.

Why it exists

IdentitySuite started as a personal need: a small e-commerce project of mine required authentication, so I built it. Some time later a company approached me to integrate their systems with an identity server tailored to their setup, and I proposed adapting what I already had. That is where the idea took shape: a library that ships a ready-to-use OIDC/OAuth 2.0 server together with an admin UI and a full set of management and monitoring tools — sensible defaults out of the box, every aspect configurable, and extensible through overrides when the defaults are not enough.

OpenIddict and ASP.NET Core Identity are excellent, well-maintained frameworks. What they are not is a finished product: you still have to wire them together, build an administration interface, design the email templates, and take responsibility for every configuration decision along the way.

IdentitySuite is that missing layer. It does not replace OpenIddict or ASP.NET Core Identity — it assembles them into something you can deploy, configure through a UI, and hand over to a team that does not want to become an OAuth 2.0 specialist first.

It is deliberately self-hosted. Identity data is the most sensitive data most applications hold; it belongs on your infrastructure, under your backup policy and your jurisdiction, not on a server you do not control.

A one-person project, stated plainly

IdentitySuite is built by one person. You will not find "our team" anywhere on this site, because there is no team — and pretending otherwise would be the first thing you should not trust about a security vendor.

Being small has real trade-offs, and they are worth knowing before you buy:

  • Response times are human, not enterprise. Support is handled directly, not through a rota — which usually means faster, more competent answers, but not 24/7 coverage.
  • The roadmap is focused. Fewer features get built, and the ones that do get built are the ones customers actually ask for.
  • Bus factor is a fair question. That is exactly what the continuity commitment below is for.

What happens if IdentitySuite is discontinued

This is the question you should ask any small software vendor, so here is the answer in writing, before you have to ask it.

Should IdentitySuite be permanently discontinued, all licenses active at the time of discontinuation will be converted into perpetual licenses for the licensed tier, at no additional cost.

In other words: the software you have deployed keeps working, with the limits you paid for, for as long as you need it. You are never one shutdown announcement away from an authentication outage.

For Enterprise licensees, a source code escrow arrangement is available on request, so that the source can be released to you if the project is discontinued.

Independently of all this, an expired subscription never disables your installation: IdentitySuite falls back to FREE mode and keeps running within the free limits. Expiry is a downgrade, never a lock-out.

These commitments are contractual, not marketing copy — see the Terms & Conditions and the License Agreement.

Getting in touch

Questions about licensing, an evaluation, or whether IdentitySuite fits your architecture are all answered by the same person who wrote the code. Use the contact form — and if you have found a security issue, please read the security page first.