Limitations
A Deployable is static files from a repository, run in a sandbox. That’s why publishing one takes minutes, and why this page exists. Read it before designing a tool.
| Can’t | Because | Instead |
|---|---|---|
| Run backend code | Stackboard runs no build and no server | Move logic to the browser, or call an existing API |
| Store data | Nowhere to write, and the sandbox blocks browser storage | Write through an API. State that must persist lives in another system |
| Hide anything in the repository | Every file it serves is downloadable | Store credentials as secrets, which never reach the browser |
| Call arbitrary APIs | The sandbox restricts network access to the proxy | Configure an API target for each origin you call |
| Run scheduled work | Code runs only while a tab is open | Use your existing job scheduler and display the results |
Network access
Section titled “Network access”The page runs sandboxed with network access limited to Stackboard’s proxy, so every API you call needs a configured target. Those calls leave from Stackboard rather than the visitor’s machine, which sidesteps CORS and VPN questions but means an API only Stackboard can’t reach is out of scope.
The entry document and the files it names have a 20 MB budget, per file and in total. Large media belongs somewhere else, referenced by URL.
Reaching outside the organization
Section titled “Reaching outside the organization”A Deployable can be shared as anyone with the link, and guests can be given one thing without joining the organization. Neither makes Stackboard a place for public sites, regulated customer data, or anything whose downtime is an incident. An admin can switch public links off for the whole organization.
Rough test
Section titled “Rough test”If the app would keep working with the network unplugged after it loads, it fits. If it needs to remember something or work while nobody is watching, it doesn’t.