For independent developers and small studios

Build it. Ship it. Support it.

The connected workspace for independent software developers and AI agents.

Plan development, run beta tests, support customers, and publish release notes from one workspace. Work on your own, with a small team, or alongside AI coding agents.

Start free · 14-day money-back guarantee on paid plans · Already have an account? Sign in

Illustrative product view
  1. SupportWaiting on Customer

    “Apple Pay does nothing on my iPad”

    Support case · Linked ticket ↓

  2. TestbenchBug

    Pay button hidden behind keyboard

    Release Candidate round · Promoted to ticket ↓

  3. Claude Code via MCP commented on the ticket: “Both reports trace to the same layout bug.”
  4. Boards · BuildingHIGH

    Apple Pay button misaligned on Safari 18

    Bug · Release: v2.4 ↓

  5. ReleasesPending

    v2.4 — Faster checkout

    Fixed Apple Pay button lines up on Safari 18 and iPad.

One platform

Everything behind your software, connected.

Independent developers end up doing the development, QA, release management, and customer support themselves. ToDoddle puts those jobs in one workspace, so a bug report, the ticket that fixes it, and the release that ships it point at each other.

The feedback loop

From customer feedback to shipped fixes.

With separate tools, every report gets copied from one service to the next. In ToDoddle it stays one connected thread, from the first message to the follow-up.

  1. Support · Testbench

    A report comes in

    A customer writes in through your Support portal or in-app SDK, or a beta tester files feedback in a Testbench round.

  2. Ticket linked

    It’s linked to the work

    Each portal request opens a support case with a linked ticket. Tester feedback can be promoted to a ticket or a support case, and the link is kept.

  3. Boards

    You fix it

    Investigate and resolve it on your board, with the original report, comments, and attachments right on the ticket. Your agent can help with this.

  4. Releases

    It goes into a release

    Set the ticket’s release. Each release lists the tickets it contains, and a Testbench round can link to the build your testers should try.

  5. Public changelog

    You publish the notes

    Write release notes in Markdown, or have an agent draft them. You decide when they appear on the project’s public changelog.

  6. Support reply

    You follow up

    Reply from the same support case. The customer gets an email with a link to read your answer, and the case closes when you resolve it.

Replies are available for portal requests. Reports sent through the in-app SDK are one-way. Publishing a release does not message anyone automatically.

Workspaces and projects

One workspace. All your products.

Your workspace is the home for your business: one subscription, one team, one set of agent connections. Inside it, each product gets its own project with its own workflow and its own public identity.

  • A project per product

    Separate boards, Project Context, Support, Testbench, and releases for each app or game you publish.

  • Each one branded its own way

    Logo, favicon, colours, fonts, and wording for the project’s home page, Support portal, and Testbench pages.

  • Hosted for you

    Every project gets a free tododdle.site address, and its home page, changelog, Support portal, and Testbench all carry your branding. From Pro, each project can use your own custom domain and drop the ToDoddle badge.

See plan limits
Illustrative example
Northlight AppsWorkspace · subscription, team, agent connections
  • Brightline CheckoutWeb appnorthlight.tododdle.site/brightline
  • TidepooliOS gamehelp.tidepool.app
  • Lumen NotesDesktop appnorthlight.tododdle.site/lumen

Public pages

Your customers see your brand. You see the whole picture.

ToDoddle hosts the pages your customers and testers use, and connects them to your private workspace. What’s public and what stays internal is kept clearly separate.

What customers and testers see

  • Support portal New requests and existing conversations, with no account needed. Access is by email link.
  • Testbench portal Applications, sign-up, test rounds, surveys, and feedback.
  • Project home and changelog Release notes you choose to publish, with New, Improved, and Fixed tags.
  • Your branding and address A tododdle.site address or your own domain.

What your team sees

  • The linked ticket Board status, discussion, attachments, and screen recordings.
  • Internal notes Kept on the support case and never sent to the customer.
  • Release details Build information and private metadata stay off the changelog.
  • Project knowledge Context, Notes, documents, and activity history.

How Support and release notes work

Agent-native by design

Your agents can do more than move tickets.

ToDoddle’s MCP server gives compatible agents more than 100 tools across the workspace, not just the board. Agents work through Agent Connections that you scope to specific projects and permissions, and everything they do is attributed to them.

  • Find, create, and update tickets, lanes, and boards
  • Read the project brief, Context, and Notes before planning work
  • Look through support cases and draft replies for you to approve
  • Draft release notes and link tickets to a release
  • Check Testbench rounds and the release each one tests
  • Claim work, log time, and request reviews
Illustrative agent session

Review this week’s new support cases, match them to existing tickets, and draft the release notes for v2.4.

  1. list_support_cases6 open cases in Brightline Checkout
  2. search_project2 cases match “Apple Pay button misaligned”
  3. add_ticket_commentNotes the duplicate reports on that ticket
  4. update_ticketSets its release to v2.4
  5. update_releaseDrafts the v2.4 release notes
  6. preview_support_replyDrafts a reply to each customer
Waiting on you Publishing to the changelog and sending customer replies stay with a person. The agent prepares them and you approve.

Built for independent developers

Professional publishing tools, without the enterprise overhead.

When you’re the developer, the tester, the release manager, and the support desk, the tools around your software shouldn’t become a second job.

Pricing

Start small. Add testing and support when you ship.

Your workspace is the plan. Every plan includes MCP access for agents. Plans scale by seats, projects, storage, and agent usage.

Starter

Free
$0/ mo
Try ToDoddle on a single project.
  • 1 seat, 2 projects
  • 100 MB file storage
  • 1 hosted MCP connection
  • 1,000 tool calls / month
Start free

For individuals

Hobby
$10/ mo
$100 / year 2 months free
For one developer building real products with an agent.
  • 3 seats, 10 projects
  • 2 GB file storage
  • 3 hosted MCP connections
  • 10,000 tool calls / month
Get Hobby

For studios

Business
$99/ mo
$990 / year 2 months free
Everything in Pro, with room for more products and testers, and priority support.
  • 25 seats, 100 projects
  • Support & Testbench on 10 projects
  • 2,500 testers, 25 active rounds
  • Priority support
  • 100 GB file storage
  • 25 hosted MCP connections
  • 250,000 tool calls / month
Get Business

14-day money-back guarantee. If your first paid plan isn’t right for you, email us within 14 days of paying and we’ll refund it in full, no questions asked. Your workspace goes back to Free: nothing is deleted, and paid features pause until you upgrade again. Refund terms

Create your workspace free, then upgrade any time from Workspace Settings → Subscription. Prices in USD.

Ready when you are

Spend more time building. Less time managing everything around it.

Bring development, beta testing, customer support, and release updates together in ToDoddle.