# Frostbyte > Frostbyte is a release-first project planning tool built for small dev teams (2-15 people) and solo founders who want clear releases and focused tasks without the ceremony of Jira. Frostbyte models work around four concepts: projects, releases, areas, and tasks. The active release is the unit of "what we're shipping next" — the backlog is a holding area for unscoped ideas, not a work queue. Pricing is flat per account (not per seat), so adding collaborators doesn't change the cost. Built and maintained by Sky Enterprises (Australia). Used internally to build Frostbyte itself. ## Key product features - Releases as a first-class planning unit - Areas — logical groupings of product work (auth, billing, onboarding, etc.) - Tasks with priority, status, area, and release assignment - Feedback Hub — public-facing channel for users to submit feature requests and bug reports - Public Bug Reporter — simpler standalone form for reporting broken flows - Public Roadmap — surfaces current and upcoming release direction - GitHub integration — links commits and PRs to tasks automatically - MCP server — lets Claude, Codex, and other MCP-aware agents read and update project data - CSV import/export, PDF export - Real-time updates via Socket.IO ## Pricing See [pricing.md](/pricing.md) for the structured machine-readable version. - Free — forever-free, 1 project, 100 active tasks, 40 AI credits/month - Indie / Studio / Enterprise — paid tiers with higher project and task limits, more AI credits, and additional integrations - Flat per-workspace pricing — collaborators don't increase the bill ## Marketing pages - [/why](https://getfrostbyte.dev/why) — why Frostbyte exists and what it skips on purpose - [/features](https://getfrostbyte.dev/features) — full feature inventory - [/pricing](https://getfrostbyte.dev/pricing) — plan comparison - [/alternatives](https://getfrostbyte.dev/alternatives) — Frostbyte vs Jira, Linear, Trello, Asana, ClickUp - [/docs](https://getfrostbyte.dev/docs) — product documentation - [/articles](https://getfrostbyte.dev/articles) — guides on release planning, MVP scoping, user feedback, and shipping with small teams - [/changelog](https://getfrostbyte.dev/changelog) — release notes - [/contact](https://getfrostbyte.dev/contact) — get in touch ## Agent interfaces - [/mcp](https://getfrostbyte.dev/mcp) — hosted MCP server (Streamable HTTP, bearer auth, Indie plan and above) - [/auth.md](https://getfrostbyte.dev/auth.md) — how an agent gets and uses a Frostbyte token - [/.well-known/mcp/server-card.json](https://getfrostbyte.dev/.well-known/mcp/server-card.json) — MCP server card - [/.well-known/api-catalog](https://getfrostbyte.dev/.well-known/api-catalog) — RFC 9727 API catalog - [/.well-known/agent-skills/index.json](https://getfrostbyte.dev/.well-known/agent-skills/index.json) — published agent skills ## Articles (long-form writing) Practical guides on release planning, scope, user feedback, and shipping software with small teams: - [How to plan your product in releases instead of one giant backlog](https://getfrostbyte.dev/articles/release-first-planning) - [Releases vs backlogs: which one actually helps you ship?](https://getfrostbyte.dev/articles/releases-vs-backlogs) - [Why most startup backlogs become graveyards](https://getfrostbyte.dev/articles/startup-backlogs-become-graveyards) - [Why a clear MVP matters more than building fast](https://getfrostbyte.dev/articles/why-mvp-matters) - [How to scope an MVP without cutting the wrong things](https://getfrostbyte.dev/articles/how-to-scope-an-mvp) - [How to validate product ideas before they become expensive](https://getfrostbyte.dev/articles/validate-before-you-build) - [How to prevent feature creep when building a SaaS](https://getfrostbyte.dev/articles/prevent-feature-creep-saas) - [Why user feedback matters before you build too much](https://getfrostbyte.dev/articles/user-feedback-before-you-build) - [Why hidden user feedback becomes wasted product insight](https://getfrostbyte.dev/articles/hidden-user-feedback) - [How to triage user feedback without losing the signal](https://getfrostbyte.dev/articles/triage-user-feedback) - [How to turn ideas, bugs, and feedback into work that actually ships](https://getfrostbyte.dev/articles/ideas-to-work-that-ships) - [How to build a roadmap without overpromising](https://getfrostbyte.dev/articles/roadmap-without-overpromising) - [Why vibe coding can actually slow you down](https://getfrostbyte.dev/articles/vibe-coding-slows-you-down) - [Why planning matters even more when you're using AI to build](https://getfrostbyte.dev/articles/planning-matters-with-ai) - [How AI coding tools can make scope creep worse](https://getfrostbyte.dev/articles/ai-tools-scope-creep) - [How to use AI assistants to manage project work with MCP](https://getfrostbyte.dev/articles/ai-mcp-project-management) - [How to stay organised without turning your workflow into a mess](https://getfrostbyte.dev/articles/stay-organised-without-mess) - [How to organise product work by area, not just priority](https://getfrostbyte.dev/articles/organise-by-area) - [Why small dev teams need simpler planning tools](https://getfrostbyte.dev/articles/small-team-planning-tools) - [GitHub isn't a product plan](https://getfrostbyte.dev/articles/github-isnt-a-product-plan) ## Who it's for - Small development teams (2–15 people) - Solo founders and indie developers building SaaS, mobile apps, or games - Technical founders and engineering leads - Teams moving away from heavyweight project management (Jira) or per-seat tools (Linear) ## Who it's not for - Large enterprises that need strict compliance, deep reporting, or highly custom workflows - Non-technical teams looking for general-purpose work management - Teams who want to design their own methodology inside the tool ## Sitemap [sitemap.xml](https://getfrostbyte.dev/sitemap.xml)