Studio for Company tools
Your people build the tools they need. You keep them in one place.
Employees make apps in Studio by asking, in their own words. Studio for Company tools brings them into one library you can see and manage: your approval, versions, who gets what, and nothing left behind when someone leaves.
Serving customers together instead? Studio for Business teams →
When everyone makes their own tools
Apps made by asking are quick to build. Without a place to keep them, a company loses track.
Without it
- Tools live on personal phones, in spreadsheets and behind private links
- Nobody knows which version people use, or what each tool can reach
- A key or password ends up written into the code
- When someone leaves, their tools and the data in them leave with them, or stay where they shouldn't
✓ With Studio for Company tools
- One library of every tool, with who made it, its versions and who gets it
- Each tool shows what it can use and which internet addresses it reaches; an update that asks for more waits
- Before you approve, see exactly what changed: what it may now reach, and every changed line
- Every tool has a maintainer; when they leave, the tool keeps working and you choose who takes it over
- Studio refuses to share a tool with a key or password written into it
- Remove someone and the team's tools and their data leave that person's devices at the next sync
From one person's tool to the whole team's
Four steps. The library is also where you add our ready apps with your own setup.
- 1
Someone builds a tool
An employee describes what they need in Studio, in their own words, and uses it right away. No developer, no app store.
- 2
They share it with the team
From Studio on their computer: Share with a team. Studio checks it first: no keys written in, and only what team apps may use. It is signed by their device and encrypted for the people who get it.
- 3
You approve it and choose who gets it
The new version waits in the library until an owner approves it. Give it to roles or named people, or mark it required for everyone.
- 4
Everyone uses the same version
People open it in the browser or in Studio on their computer. Updates reach them by themselves; withdraw a version and it goes back to the last good one.
What a Company tools team gets
- Your people build tools in Studio by asking, in their own words; give the ones who build the Builder role
- A builder's versions wait for your approval, with what changed shown line by line; publish, pin, withdraw and see every version
- Choose who gets each tool by role or by name; required tools install by themselves
- Tools open in the team's own space in the browser and in Studio on a computer, apart from personal apps
- Shared records between the people using a tool, encrypted for each device
- A tools overview: who maintains each tool, how many devices have it and how many are on an older version
- Categories, search and an activity export: who published, approved, installed or removed what
Next: team apps inside the phone app, and adding apps from the web and the phone.
Our apps, your setup
Some of our Gallery apps can join your library with your own lists and rules. The library keeps only a reference to our app and your setup file, so our updates keep reaching your team. If a new version would ask for more than you allowed, it waits until you add it again.
- 🏷️ Price Book: the items your company buys, with target prices, stores and categories. Never anyone's logged prices.
- ⏱️ Timesheet: your projects with clients and rates, rounding, overtime, breaks and the week's first day. Never anyone's hours or pay.
A setup holds lists and rules, never code: Price Book's items, target prices and stores; Timesheet's projects, rates, rounding and overtime. Members see “Your team's setup” once and choose to use it.
Who sees what
Four roles, fixed for the preview. The service checks every request against them.
| Role | Sees | Can do |
|---|---|---|
| Owner | The whole library: every app, its versions and who gets it; the members, their devices and the activity; how many shared records each app keeps, never their content. | Publish, approve, withdraw and mark apps required. Add, approve and remove people and devices. Clear an app's shared records. Delete the workspace. |
| Co-owner | The same as the owner. Joins by email invitation only. | The same, except deleting the workspace, inviting co-owners or removing the owner's devices. A co-owner's versions wait for the owner's approval unless the owner turns that off. |
| Builder | The apps given to them, and the apps they publish. | Add apps to the library from Studio on a computer; a builder's versions wait for the owner's approval unless the owner turns that off. Use the apps. |
| Member | The apps given to them, and the shared records of those apps. | Install and use those apps; required ones install by themselves. |
Privacy and security, in plain words
What is encrypted, what our service can see, and what you control.
An app's files are signed by the publisher's device and encrypted separately for each device that gets it. Studio checks the signature and every file before it installs anything. Our Gallery apps come from priorstates.com only as PriorStates signed them.
Team apps run in their own space, apart from your people's personal apps and data, and can reach only the internet addresses their card lists. An update that asks for more waits until the person allows it.
It stores app files and shared records only encrypted, so it can't read them. To run the library it does see email addresses, names, roles, each app's name, versions, what it may use and its list of files, who published it and when, and the activity.
A team app's shared records are encrypted on the device that writes them, one copy for each device that may read them. We store the encrypted copies, who wrote each record and when, which app and list it belongs to, and its size, never the content.
Removing a person or a device stops their access at once, and their team apps are removed at the next sync. Each device is removed on its own, so a lost laptop doesn't affect the other devices. What someone has already seen can't be taken back.
Owners, co-owners and people invited by email sign in with a code sent to their email. A code lasts ten minutes and allows five tries.
Turn on a key backup and your browser seals it with a passphrase you choose (at least 12 characters) before anything is uploaded. We never receive the passphrase and can't open the backup, so we can't reset it for you either.
The Team database is backed up every hour, encrypted. Backups are kept for 7 days on the server, and an encrypted, private copy for 30 days in Amazon S3 (US East). We don't add usage analytics or send team records to AI services.
Your personal Studio stays separate
Studio for Teams is a separate place with its own sign-in and its own storage. Your personal apps, Spaces, data and Google Drive backups are not moved, copied or shared, and nothing changes in the Studio app you already use.
What the preview includes, and what it doesn't yet
Free during the pilot. These limits apply to every team.
✓ Included
- A team library: publish, versions, approval, withdrawal, required apps, categories, search and an activity export
- Our Gallery apps with your setup: Price Book and Timesheet
- Team apps in the browser (the team's own space) and in Studio on Windows, Mac and Linux
- Shared records between the people using a team app
- One computer running an app's Python backend for the whole team
- Joining by email invitation or in person by QR code; several devices per person; key backup
… Not yet
- Team apps inside the phone app
- Adding apps from the web or a phone: for now from Studio on a computer
- Apps that use the camera, the microphone, location or other apps' data; our apps that need public links (Order Form, Sign-up Sheet)
- No production availability guarantee, no public sign-up and no paid plan
Pilot limits
- 30 devices per team: people's devices and key backups together
- 20 apps in the library, 10 of them required
- 100 MiB of apps per team, up to 5 MiB per version
- 2,000 shared records per app, 32 MiB for all of them
- 20 open invitations and QR codes at a time
- 1,000 recent activity entries, kept up to 90 days
Questions
Do my people need to install anything?
No. Team apps open in the browser, in the team's own space. People who use Studio on Windows, Mac or Linux can open them there too. Inside the phone app they come later.
Can a team app see someone's personal apps or data?
No. Team apps run apart from personal Studio, with their own storage, and personal apps never get the team's keys or records.
What happens when someone leaves?
Remove them from the team. At the next sync their team apps and those apps' data are removed from their devices, and new shared records no longer reach them. What someone has already seen can't be taken back.
If we use one of your apps, who owns the data?
You do. We provide the app's code and its updates; your setup and everything your people enter stay in your team, encrypted for your devices.
What does it cost?
It is free during the preview, within the limits above. There is no paid plan.
Try it with your team
The preview is by invitation, and there is no public sign-up. Write to us with your company's name, what you want your people to use, and how many people would use it.
Or write to service@priorstates.com
Serving customers together instead? Studio for Business teams →