Hosted Studio

The hosted Studio runs at a single Flexkit address. You sign in once with your Flexkit account and can open any project you are a member of, across all your teams, from the project switcher in the navbar. Nothing is installed or configured per project: the Studio renders whatever schema each project has deployed.

Sign in

Open flexkit.app , or click Open in Studio in the project header of the Dashboard, and sign in with the same provider or email you use for the Dashboard. After signing in, the Studio opens the project you used last on this browser, or the first project in the list when you are new.

If you are not a member of any project yet, the Studio shows a short notice with a link to the Dashboard, where a team owner can create a project or invite you.

Switch projects

The project switcher lists every project you can open, grouped by team when you belong to more than one. Switching projects keeps you signed in; only the deployed schema, your role and your spaces change. The Studio remembers the last project you opened and returns to it next time.

A project URL you receive from a teammate opens that project directly, after login if needed. Opening a project you are not a member of shows a No access notice with a link back to your own projects.

Hosted or self-hosted

Both run the same @flexkit/studio package and talk to the same project API, so your data, roles, spaces and deployed schema are identical in either. Teams self-host when they want the Studio inside their own application, on their own domain, or mounted under a path; see the quickstart. Developers can also keep using a self-hosted Studio locally while business users work in the hosted one.

Custom tools and code skills are not affected by where the Studio runs: they are served from your own backend and developed with flexkit dev; see custom tools.