WHY WE BUILT IT
Every app your colleagues build, behind one door.
cyantula grew out of one problem: self-built apps that nobody can safely share. Here is why we built it and where we are today.
Why cyantula exists
Colleagues now build small web apps themselves, most of them AI-generated, and none of those apps handle authentication. IT cannot review every one, and the person who built a tool in an afternoon cannot be expected to become an ops engineer for it. So the tools stay on a laptop or get shared over chat, where nobody controls who opens them.
cyantula sits in front of every app as an authenticating gateway and runs the app behind it. The app never sees a password.
In early access in 2026, onboarding our first ten teams by hand.
Who we built it for
cyantula is for teams where colleagues already build their own tools, and where one IT person can no longer review every app by hand. If that sounds like your company, the gap we close is already open somewhere in it.
- The engineering lead who knows there are self-built apps running somewhere, and cannot name all of them.
- The IT person who does not want to become the bottleneck that every internal tool has to queue behind.
- The colleague who built something useful in an afternoon and should not have to bolt on login, deploys and backups before anyone can safely use it.
Where we are now
No self-serve signup yet, we onboard every team by hand. Sign-in is locked to your Google Workspace domain.
That is honesty, not a weakness: a person walks you through your first apps, so you know exactly what runs behind your login before it does.
Talk to the people building it
Book a demo for a walk-through, or get early access to be one of the first teams we onboard by hand.