Your teams build apps in a day. Run them inside your own cloud.
People across your company are already building tools with AI. Pikku Studio gives every one of them sign-in, permissions, a real database and a review before release, and Enterprise, coming soon, is meant to run all of it inside your company’s own cloud account.
- Your own cloud account, coming soon
- Bring your own AI
- Pikku Studio itself is free
It works. That was never the problem.
The tool someone built last month does its job. Ask three questions about it and the trouble shows.
Where it lives
A personal account paid on someone’s card, with the database password sitting in a file next to the code.
Who can open it
Anyone with the link, or everyone who knows the one shared password that has been in a chat for months.
What it holds
Nobody has written down which of its columns are personal data, and the security questionnaire is on its way.
Now multiply that by every team that worked this out in the last year. Your IT team can’t take on every one by hand, and banning them has never once worked.
Keep the screens. Replace what was improvised.
Nobody redraws a screen and nobody is retrained. What changes is the part behind the screens, which was the risk all along.
The screens your people use
The pages, layout and styling of the app you already have don’t change.
Everything behind them
Every place the app reaches a database or another system becomes a clear action with a declared permission. Nothing is thrown away: you are writing down what it was already doing. Systems already in production skip this and get a layer on top instead.
One release. Everything else comes with it.
The person who built the app sets up nothing, requests nothing and waits for nothing. All of this arrives with the release, because it is what a Pikku Studio app is, not a checklist somebody works through afterwards.
Named accounts and roles
Everyone signs in as themselves. No shared passwords.
Permissions on every action
Declared once, checked every time anyone, or anything, asks.
A real database
Postgres, with every change to its layout recorded and applied on release.
Its own address, with HTTPS
A proper internal web address with a proper certificate.
Logs of who did what
Every request, every change and every AI call, traced back to a person.
Clicked through before release
Each journey is walked through as each kind of user, in a real browser.
A person signs off
Changes that could break something wait until someone has looked at them.
Undo a bad release
Go back to the version that worked, and it refuses if the database no longer matches.
Practice copies
Try a change on its own copy, with its own database, address and secrets.
One door for AI
Every model goes through one gateway, with a budget per team and every call counted.
Nothing to migrate. It goes on top.
Point Pikku Studio at the systems you already run. It reads their API descriptions and puts one layer over them, with sign-in and permissions on every action. The systems underneath don’t change and nothing is switched off.
Sign-in on systems that never had it
An internal service that trusted anyone on the network now checks a named person, without the team that owns it changing anything.
Several systems, one request
What an app actually needs is usually three systems at once. Combine them here once, instead of in every app that wants it.
AI that passes the same checks
The tools an AI assistant uses come from the same actions your staff use, so it meets the same permissions, not a copy of them.
and the old screens? Once the systems sit behind one layer, a dated front end can be rebuilt on its own, drawn to match the one your people know, down to the labels and the order of the fields. The old one stays up beside it until you decide otherwise.
Three services. Then it is yours.
Planned, the whole installation inside your cloud account is these three services, with nothing hiding behind it.
From there, apps deploy to your own machines or to a cloud you choose. The code sits in your own Git from the first day, on the MIT-licensed Pikku framework.
Read the source- 1
Logs and traces
OpenObserve. Point it at an instance you already run, if you have one.
- 2
One gateway for AI
LiteLLM, in front of every model: open models on your own hardware, a provider you choose, or a different one per project.
- 3
The Pikku Studio Cloud service
Releases, reviews and undo, with its own Postgres database underneath.
What isn’t built yet is still being decided
The left column runs on Pikku Studio Cloud today. The right column is the edition for your own cloud, which is coming soon: scoped, not shipped.
Works today
- Deploying to Pikku Studio Cloud with everything on this page attached
- One layer over the systems you already run, reachable by apps, AI assistants and commands
- Permissions kept as data, so access is taken away without a release
- The release review and undo
Still open
- The packaged edition for your own cloud: coming soon. Its design document is marked “scoping”; ask and we will send it to you.
- Company sign-in (SSO) with your own identity provider: coming soon. It isn’t switched on yet, so we don’t claim it.
- The offline licence file an install inside your network checks against.
- Certificates without Cloudflare. The deploy path doesn’t touch Cloudflare; certificates still do.
- SOC 2, ISO 27001 and contractual round-the-clock support. We have none of these today.
Your security reviewer would find all of this in an afternoon. Better they read it here first.
Tell us what it has to meet.
Sign-in with your provider, how certificates are issued without the public internet, which cloud it has to sit in, what your auditor expects to be handed: tell us yours and they get built in. We would rather hear them on a call than in a questionnaire.
Deploy one today. Run them all yourselves when you’re ready.
Start with Pikku Studio on one team’s app, and deploy it to your own servers or to Pikku Studio Cloud. Moving inside your own cloud later changes where it runs, not how it works.
The edition for your own cloud is coming soon. It starts with a call and an honest answer about timing.