Developer sandbox
The developer sandbox is a free workspace for building and testing a Kit without touching a production workspace.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Members | 5 at most |
| Model quota | 20 assistant runs per day |
| Number | One per account |
| Inactivity | Deleted after 90 days without activity, after a 7-day recovery window |
| Production use | A sandbox cannot be converted into a production workspace |
Activity means a message or an audit event; the 90-day clock runs from the last one. After the deadline the workspace is pending deletion for 7 days and can still be recovered before it is removed.
Create it
Section titled “Create it”In the developer portal open Developer, then Sandbox, and create it. You can also create it
through the API; calling it again returns your existing sandbox. Create a developer token
in the sandbox workspace: ketvia kits dev only works with a token created there.
Develop in it
Section titled “Develop in it”ketvia kits dev installs your manifest into the sandbox and moves its endpoint URLs onto a public HTTPS tunnel that
you run, so Ketvia can reach your laptop. See CLI. Ketvia does not operate a relay or a
tunnel.
How it differs from a production workspace
Section titled “How it differs from a production workspace”- It is capped as described above; a production workspace has no member cap and the platform’s normal run limits.
- It exists for development: dev installs register private Kit versions in the sandbox, not unlisted or directory Kits.
- It is not retained forever and cannot be promoted. Publish and install your Kit in a real workspace when it is ready; see Distribution and installs.