Developer Docs

Use these docs when you are changing OpenPost itself: backend routes, platform adapters, frontend components, generated clients, MCP tools, billing infrastructure, database migrations, tests, or release behavior.

Developer docs are separate from user-facing docs and self-hosting docs. They can assume repository access, local toolchains, and willingness to run checks.

Start here

• Development Setup gets the repo, frontend, backend, and docs running locally.
• Architecture explains the main boundaries.
• Contributing covers contribution workflow.
• Testing covers local and CI checks.
• Releases and Versioning covers SemVer, production releases, and failure handling.

Backend and API

• Backend covers Go backend conventions.
• API Reference renders the generated OpenAPI spec.
• API Tokens documents one-time secrets, expiry, scopes, workspace boundaries, and revocation.
• Background Jobs covers durable job behavior.
• Platform Adapters covers provider integration rules.
• Billing and Usage covers entitlements, usage counters, and hosted billing primitives.

Frontend, MCP, and launch work

• Frontend covers SvelteKit app conventions.
• Image Editor Completeness tracks the source-grounded implementation and verification contract for editor polish.
• MCP and ChatGPT App covers tool-server and Apps SDK integration notes.
• Production Architecture records shared hosted and self-hosted architecture, provider verification, and release checks.

Adjacent docs

• If you are using OpenPost through the web app, CLI, or MCP client, start with User Docs.
• If you are deploying or operating an instance, start with Self-Hosting Docs.