Relpin starts from a real project, not a locked visual canvas. The fastest path is to open Studio, choose a starter, preview it, and promote a pinned release when the app is ready.
Before you start
You need a Relpin account and access to an organization workspace. During open beta, some organizations are invitation-only.
Use a starter when you want a working app quickly. Use an empty project when you already know the route structure, SDK calls, and data model you want.
Create the app
- Open Studio and choose the target workspace.
- Create a new app from a template.
- Review the generated project files.
- Start the preview.
- Make a small copy or UI change.
- Confirm the preview updates.
The browser is not the source of truth for the app. Relpin keeps project files, preview execution, and publish state on server-side paths so human and agent edits converge through the same contracts.
Preview the app
Preview runs the app with the same governance boundaries the publish path relies on: scoped runtime context, server-side data access, and environment-aware configuration.
If preview fails, treat the error as authoritative. Do not work around missing auth, missing bindings, missing data access, or invalid environment state in browser code.
Publish the first release
When the app is ready, publish creates a pinned release artifact. Promote it through the environments your organization uses, usually DEV, TEST, and PROD.
The important property is repeatability: a promoted release should point to known content, known configuration, and known governance state.
Next steps
- Read Code-first apps.
- Read Releases and promotion.
- Try Use OpenCode in Studio.