Developers
You build and publish apps in PhiWebs Studio without writing code. This section is for when something outside the studio needs to work with those apps: a script, another service, your own server or an AI assistant.
What you can do
| You want to… | Start with |
|---|---|
| Read or write a published app’s records from your own code | API reference |
| Know how an app gets from the studio to its public address | How it works |
| Understand how AI is used and paid for | AI |
| Know the size and usage limits before you hit them | Limits |
| Host an app on your own server | Self-hosting |
| Manage your workspace from Claude or another MCP client | Integrations |
Two different identities
Keep these apart; most confusion comes from mixing them up.
- Your PhiWebs account is how you and your workspace members sign in to the studio and the account app. It is also what an AI assistant acts as when you connect it to your workspace.
- An app’s visitors sign in to that app only. Each published app keeps its own people list, its own roles and its own sessions, separate from every other app. See Visitor sign-in and Sign-in, roles and people.
A workspace member gets no role inside a published app just by being a member. Roles come from the app’s own people list.
Making apps
Apps are made in the studio, not through an API. There is no endpoint that builds, changes or publishes an app for you. Open the studio at studio.phiwebs.com and describe what you want.
PhiCo, the earlier assistant, is retired, and so are its page and composer endpoints. Apps are now made in PhiWebs Studio.