Self-managed backends
llms.txtlists every page for an agent
Who it is for
You keep state in a directory, or in a cloud storage bucket you run.
Features
- The backend works as it is, with nothing to move
- A target lock per stack keeps two pull requests from updating one stack at once
- The stack export after each update is the record the graph and checks read
Every setup gets
- One preview note on every pull request
- Updates of the previews you approved
- No overlapping or stale updates
- Re-preview from a comment
- Scheduled drift checks
- Separate identities to preview and to update
- Policy on every preview, CrossGuard included
- An audit trail in your own repository
- Secrets stay [secret] in notes
- Your backend and your runners, as they are
Differences
- plywood keeps its approvals and locks on the chant/lifecycle branch of your repository, next to the backend.
First step
Then read
- How-to
- Add plywood to a repo
- Explanation
- Locking and stalenessArchitecture
- Reference
- BackendsConfiguration