IYA.AI

The problem it took on

Your information is not in one place you control. It is scattered across every service that ever collected it, and none of those services work for you. A person notices this only when they try to answer a simple question: who has what about me, and on what terms.

IYA.AI treated a person's information as a managed asset rather than something left wherever it landed, with AI at the center to organize it and a ledger underneath to record who was granted what.

What Frank built

• The architecture, written before any team was hired.
• The core system himself: the API-driven service, the user model and the initial deployment to AWS.
• The operational base around it, including DNS and email, so the product ran as a service rather than a demo.
• The development team, built and led on top of that base.

The core system and web application were deployed. Native iPhone and Android applications were in development.

Why the order matters

A platform gets its shape in the first few weeks, from whoever writes the core. A team hired before that shape exists spends a year finding out what it was supposed to be.

On IYA.AI the same person wrote the architecture, built the core and the APIs, and put the first version on AWS. The team arrived to a working system, not a specification.

Where it leads

IYA.AI's thesis carries directly into Jellybean, the data company built on the position that your personal data is yours, and into the wallet identity work behind the Austin civic identity entry.

It is not offered as a running system today. It is on this page as the record of where a current capability came from.