StudioCloudEnterpriseDocs

Internal software, built inside your walls.

Your teams describe the tools they need. Studio's AI builds them as real applications on the Pikku framework, running inside your network. It works fully offline, air-gapped included.

Talk to usSee how it is contained
The Pikku chameleon rests inside a hand-drawn enclosure, drawn in cream line on dark paper, with a single closed gate.Your networkgate closed

Everything happens inside the line you draw.

Studio, the applications it builds, the data they use and the keys that protect them all run on infrastructure you control. The outside world is an option you can leave switched off.

Vertical version: a boundary labelled your network holds Studio at the top and apps, data, a secrets vault and your people below. Under the boundary, a dashed optional path leads to Pikku Fabric, and the internet is marked not required.Your networkStudioAppsSecrets vaultDataYour peoplePikku Fabricoptionalthe internet is not required
Runs in your network
On your servers and workstations, behind your existing controls.
Fully air-gapped
Studio and its apps work with no internet connection at all.
Licence checked offline
Your licence key validates on your own machine. There is no phone-home.
Hosting is optional
Pikku Fabric can host and deploy your apps, if you choose it.

Every credential in one vault. Every access on the record.Keys live in a separate process, not in your code or your configuration. Each time an app asks for one, the request is written to an audit log in which every entry is chained to the hash of the one before, so any edit to history is detectable. The vault can also be backed by the one you already run, such as AWS Secrets Manager or HashiCorp Vault.

Vertical version: app code at the top sends a request down across the process boundary to the vault, which answers it and records the access. Below, audit entries are chained top to bottom by their hashes.App codeVault · separate processProcess boundaryasks for a keyanswered, loggedor AWS / HashiCorpAudit logEntry 1Entry 2Entry 3its own hashhash of entry 1hash of entry 2chainedby hash

Ownership

What Studio builds is ordinary TypeScript. It belongs to you.

Every application is built on the MIT-licensed Pikku core. Your engineers can open it, review it, extend it and run it without Studio. If you stop working with us, your software keeps working.

When you want managed deployment and hosting, Pikku Fabric is available. It is never required.

What we haven't confirmed yet.

We would rather mark these than guess. Tell us what matters to you and we'll say where each one stands.

  • Single sign-on and SAMLto confirm
  • Roles and permissionsto confirm
  • Support service levelto confirm
  • Onboardingto confirm
  • On-premises installation helpto confirm
  • Model choiceto confirm
  • Pricingto confirm
Talk to us

Talk to us

Tell us about your estate.

Where it would run, who would build with it, and what has to stay inside. We will reply personally.

Working on your own, or just exploring? Pikku Studio OS is free and runs on your laptop.

Get Pikku Studio OS