Build with an agent
Read these public sources
Section titled “Read these public sources”Start with llms.txt. Fetch the current feature status
before writing DSL. It defines the implemented subset and explicit limitations.
Every page has a matching /markdown/<page>.md URL. The complete text is
llms-full.txt. No page needs a dashboard session.
Bootstrap
Section titled “Bootstrap”The human creates a verified platform account and issues a scoped agent key.
Use the installer and bfast login --token-stdin with a secret
manager pipe. Never place the key in a tool argument, app source or URL.
curl -fsS https://dash.backend.fast/install.sh | shbfast versionbfast whoami --jsonBackend operations use public HTTPS. No SSH access, node filesystem or repository checkout is required. Download the source examples directly from this site:
mkdir -p agent-countercurl -fsS https://docs.backend.fast/examples/simple-counter/backend.fast \ -o agent-counter/backend.fastbfast deploy --name agent-counter --tier small ./agent-counterbfast inspect --json agent-counterUse a fresh name if agent-counter already exists. Read the complete
quickstart for test users, protected requests, update and cleanup.
Execution rules
Section titled “Execution rules”- Put flags before positional arguments. Use
--jsonfor machine-readable output. - Read the stored app URL from
inspect. Never derive it from the display name. - Keep the declared DSL app name unchanged during update.
- Preserve model/private schemas during normal update. Do not assume arbitrary migrations.
- Record operation IDs. A lost reply does not prove failure. Inspect the accepted operation before submitting another mutation.
- Use a platform key for app management. Use an app-user token for business routes.
--verifiedis an owner attestation for test users. Real public signup needs verification mail.- Treat app deletion as retained data. Do not promise a permanent purge or refund.
- Reject unsupported features explicitly. Do not invent API commands, DSL syntax, OAuth providers or CORS behavior.
Feature choices
Section titled “Feature choices”Use models and queries, auth, events/jobs, and files when their current subset matches the requirement. Limits lists current resources and payload bounds. Troubleshooting describes expected failure responses.
Small is 130m CPU and 256 MiB. Medium is 250m and 512 MiB. Fresh native apps have no commercial stored-user count or small global session count. Resource and operation guards still apply. Accounts initially share 10,000,000,000 object bytes.
The platform remains in development. High availability, arbitrary packages, general external network access, Apple login, managed cross-origin browser SDK policy and automatic customer restore are not supported promises.
Definition of done
Section titled “Definition of done”Check the operation result and public health. Create or use a scoped app user. Verify an authenticated write/read. After update, verify the same app ID, URL and acknowledged data. Confirm dashboard visibility. Report unsupported features and retained data clearly. Keep credentials out of generated reports.
Source provenance
Section titled “Source provenance”source.json records the committed source revision and SHA256 values for the feature matrix and downloads. The public projection excludes operator runbooks and private node state. Documentation releases update that snapshot; they do not make this site a live control API.