Mateusz Konik

• I know many countries (especially in the European Union) are moving toward requiring AI-generated content to be distinguishable from human-generated content. Gemini already does this with images, and now Claude does it with text.

• Social platforms are also creating their own identifiers that can detect and label AI-generated content, such as AI labels on X and LinkedIn.

I understand all sides of this:

Governments want to prevent misinformation.
AI companies can use it as a way to promote their tools.
Companies and SoMe platforms can distinguish AI-generated content from human-created content.
And AI tools can essentially create their own trademark on the content they generate.

I talk to founders every week and the pattern repeats. The team needs login, someone says "how hard can a login form be," and two quarters later they are maintaining an identity system nobody wanted to own and the actual roadmap is on fire.

The problem is that auth looks like one feature but it is actually five products stacked on top of each other:

• Every sign-in method your users expect (passkeys alone took our team over 800 engineering hours to get production ready)

• Session management that survives a real security review, which arrives with 40 questions you have not thought about

• Token infrastructure, issuance, rotation, revocation, the part that pages someone at 2am

• Permissions, because plain roles stop working the moment your product grows

• And now identity for AI agents acting on behalf of your users, which no in-house auth from two years ago was designed for

Each of these is somebody's entire company. Your team will build all five as a side quest, and then maintain them forever.