Repository navigation
Home
Felipe Inoue edited this page Nov 9, 2026
·
4 revisions
Your project's setup, in one place you host. Templates, scripts and files you pull onto any machine — self-hosted, no subscription, no third party.
- One place for the files a project needs. Agent instructions, editor rules, skills, scripts, any text or binary file.
-
Publish once, apply anywhere. A folder becomes a template; the next
machine gets
eznit template apply <id>. - With or without AI. Starters for opencode, Codex, Copilot, Cursor and Windsurf; plain shell and editor configuration travels too.
- Yours. Bytes on your disk, your PostgreSQL, no third-party account.
Pre-1.0 and unhardened. Read the security status in the README before exposing this beyond
localhost.
| Step | Command | What happens |
|---|---|---|
| 1. Run it | make setup && make up |
Docker builds and starts the API, the UI, PostgreSQL and the migrations |
| 2. Write a starter | eznit template init --kind opencode --target ./demo |
Files appear in ./demo; no server, no account |
| 3. Create an account | eznit signup |
The first account on the instance is its admin |
| 4. Publish it | eznit template publish ./demo --public |
The folder is in the shared catalogue |
| 5. Apply it elsewhere | eznit template apply <id> --target ../other-project |
The files are written; the variables are asked here |
| 6. Take it offline | eznit template export <id> -o setup.eznit |
One file; apply --from-file needs no server or account |
The full walkthrough, including the release-bundle and no-Make paths, is on Getting Started.
| I want to… | Read |
|---|---|
| try it in five minutes | Getting Started |
| publish and apply a template | Templates and skills |
| look up a command or flag | CLI Reference |
| configure every variable and secret | Configuration |
| know what runs on which OS or shell | Platforms and shells |
| see what is planned | Direction |
| develop or cut a release | Development · Releases |
| fix an error | Troubleshooting |
- README — the short project overview
- ARCHITECTURE — the request path, the data model, where the bytes live, where a change belongs
- Roadmap board — planned work; the issues are the source of truth
- Releases — downloadable archives
- Contributing
The wiki's source lives in the repository at docs/wiki/, so it is reviewed like
code and synced with make wiki_push. Edit a page there through a pull request
rather than only in the wiki UI, or the next sync will overwrite it.