TinyCase
Back →

For AI agents: see llms.txt for a full documentation index. Every page is also available as markdown — request the URL with a .md suffix or an Accept: text/markdown header.

Docs / Getting Started / What is TinyCase

What is TinyCase

Core concepts: cases, customers, docs, and the AI tools.

What is TinyCase

TinyCase is a lightweight support tool for solo developers and small teams —
a place for customers to submit issues and a place for you to answer them,
without email-channel plumbing or enterprise-helpdesk overhead.

Core concepts

  • Case — one customer issue, from submission to resolution. Has a
    status (open, pending, resolved) and a thread of messages.
  • Customer — created automatically from an email address the first time
    someone submits a case. No signup required on their end.
  • Message — a reply in a case. Either customer-facing or an internal
    note visible only to staff.
  • Docs — your knowledge base. Public collections power the customer-facing
    docs site and AI chat; internal collections are staff-only.

Free vs. Pro

Free covers the basics: a contact form and an inbox to read submissions in.
Pro unlocks the parts that make it a two-way conversation:

Free Pro
Staff seats 1 10
Receive submissions Yes Yes
Reply in-app No — reply via email instead Yes
Customer case portal No Yes
Docs & knowledge base No Yes
AI tools (draft, summarize, similar cases, doc search) No Yes
Custom domain No Yes

On Free, a new case still emails you — you just reply from your own inbox
rather than through TinyCase, and the customer never gets a page to check
back on.

Where things live

  • tinycase.app/cases — your case list (staff)
  • tinycase.app/docs — your knowledge base (staff)
  • tinycase.app/s/<slug> — your public submit form (customers)
  • your case portal — a private link customers get after submitting, or at
    your custom domain if you've set one up

See Submitting and tracking a case and Managing cases as staff for
what each side actually looks like.

Ask a question