Bring what you run on today — the spreadsheets, the shared drive, the group chats, the app nobody can maintain. Pikku Studio turns it into a platform your team and your customers sign in to.

  • Free
  • Runs on your computer
  • No account needed
  • Works offline with a local model
See what people have built with it
A spreadsheet of bookings, a folder of prices and a chat message flow into a laptop, where they have become a bookings app. The Pikku blob peeks over the screen, and the Wi-Fi sign is crossed out.BookingsYoga weekend12Team offsite30Pottery, Saturday8Bookbookings.csvprices 2026can we move Friday'sgroup to 3pm?no Wi-Fi? use a local modelyour app lives here, on your own disk

Software for your business was always out of reach.

Sooner or later every business needs a platform of its own. Getting there has meant one of two roads, and neither was built for you.

  1. priced for someone else

    An agency or a tech team

    It works, and it is priced for companies that already have the money. Months of meetings, a quote with a comma in it, and another bill every time something needs to change.

  2. now what?

    Vibe coding it yourself

    It is cheap, and it starts with a blank box and a thousand decisions you did not know existed: which database, which sign-in, where it runs, how people pay. Most of it ends as a demo that works on one laptop.

  3. one step at a time

    Pikku Studio

    A path instead of a blank box. It starts from what your business already runs on, asks about the parts you have not thought of yet, and settles the technical questions for you — the way a good tech team would.

How it compares to other AI builders, feature by feature

From what you have to what you run on.

Not an afternoon demo, and not a six-month project. A week, with you deciding at every step.

  1. Day 1

    It reads everything

    The spreadsheets, the documents, the chat exports, the screenshots of the app you have now. It works out who your customers are, what they buy, and what your team does all day.

  2. Days 2–3

    You agree the plan

    It comes back with the screens, the accounts and the rules, in plain words, one milestone at a time. Nothing gets built until you say yes.

  3. Days 4–6

    It gets built, and checked

    One AI builds it and a different one checks the work, because nobody marks their own homework. Every screen is clicked through as each of your people before anyone else sees it.

  4. Day 7

    You run on it

    Your team signs in, your customers sign in, and the spreadsheets retire. When something needs to change, you ask for it the same way you asked the first time.

Everything you never got round to building.

A spreadsheet cannot take a booking, and a vibe coded app rarely gets past one laptop. These are the parts that make it something other people can use, and you do not build any of them.

  • Real accounts

    People sign in as themselves, with an email, a Google account or a one-time link. You are not handing out one shared password.

  • One payment, or every month

    Card payments and subscriptions through Stripe — renewals, failed cards and cancellations all handled. You do not wire any of it up.

  • A web address

    The day it deploys it has a working address and a certificate. Point your own domain at it when you are ready: on your own servers any time, on Pikku Studio Cloud from Indie up.

  • A back office to run it from

    Change your prices, your hours and your content yourself, on a screen built for it. You are not going back to the agent every time something moves.

  • Companies, not just people

    One app can serve many businesses, each with its own people, its own data and its own bill. Roles decide who is allowed to change what, and nothing crosses between them.

  • It sends the emails

    Every confirmation, reminder and receipt your app needs gets written for it — in each language you support, on a layout that already matches the app.

Pikku Studio stands on its own. The cloud is optional.

Studio runs entirely without us. What it builds is standard code on the Pikku framework, which is MIT licensed — no proprietary runtime, nothing that only works on our servers. Deploy it wherever you like, and move it whenever you like.

free, on your computer

Build on your computer.

Pikku Studio is a complete app of its own. Build the whole platform on your machine with no account with us. Use an AI provider’s key, or connect a model running on your own hardware and work fully offline.

Free, with its source open to read. Roles, permissions and the security center come with it — none of it sits behind a plan.

Download Pikku Studio
your servers, your bill

Deploy to your own infrastructure.

Your app is yours to run. Put it on your own servers or in your own cloud account, with your own database, and keep every byte of it where you decide.

Nothing comes to us. You pay your provider directly.

Read the framework’s source (MIT)
pay as you go

Or let us run it.

One step from your computer to a real web address, with the database and certificates handled. Serverless, so you pay only when people use it, or on a server that stays on.

Signing up puts free credit in your account, and after that you pay as you go: up to five projects, with everything but teams. Indie adds teams, your own domain and monthly credit. Business adds company sign-in, which is coming soon. See the price list

Start in the cloud

Rolling it out across a company? Business will add company sign-in (SSO), for your team and for the apps you publish inside the company, and Enterprise will put Pikku Studio Cloud inside your own cloud account. Both are coming soon. Talk to us

Straight answers

Do I need to be a developer?
No. If you can explain how your business works, you can do this. Download Pikku Studio and start with the files you already have, or sign in and build it in the browser with nothing to install. If you already use Claude Code, Cursor or Codex, you can start from there instead.
Does it really work offline?
It can. Connect Pikku Studio to a model running on your own computer and nothing leaves the machine. How well that goes depends on your hardware — a larger model needs a more powerful computer — so most people start with an AI provider’s key and switch later if they want to.
What if the AI gets it wrong?
It will sometimes. So a second opinion checks the work, and it is never the one who did it. Before anything goes out, someone clicks through it the way a customer would. Every change starts as a plan you approve, so anything that slips through, you send back the same way.
Will my customers see each other’s things?
No. Every app comes with real accounts and rules about who sees what. Your team sees everything, each customer sees only their own, and somebody clicks through it as each kind of customer before it goes out.
Am I going to get a bill I did not agree to?
No. Pikku Studio itself is free, and so is running what it builds on your own servers. The AI is the one part you bring: an AI provider’s key, billed by them, or a model on your own computer that costs nothing. You pay us only when you deploy to our cloud. Signing up puts free credit in your account; after that you pay as you go, or choose a plan with monthly credit, spent on requests, servers, storage and AI as they happen. Monthly credit is used first, and you top up only if you choose to.
Who owns the code?
You do. Your app is ordinary code in your own repository, built on the MIT-licensed Pikku framework. Run it on your own servers or on ours, and leave whenever you like — there is nothing proprietary to untangle.

Bring what you have. Run on it next week.

Download Pikku Studio, free, and start with the spreadsheet you opened this morning.

Pikku Studio is free, for good. Bring your own AI, and pay us only when you deploy to Pikku Studio Cloud.