Sayr is a source-available, self-hostable project management platform that pairs an internal task board with a built-in public feedback portal, so a product team can work privately while its users submit feedback, vote on features, and watch progress from the same tool.

What it is

Sayr is a TypeScript application built on TanStack Start 1.x, React 19.2+, Hono 4.10+, and the Bun runtime. It presents one board with two views: the internal team sees everything, and the public sees only the items the team marks as visible. Each organization can expose its board on a dedicated subdomain ({org}.sayr.io on the hosted edition, or a domain of the operator's own choosing when self-hosting). Sayr ships in three editions — Community for free self-hosting, Cloud for the hosted service at sayr.io, and Enterprise as a licensed self-hosted edition — and the Docker images are edition-locked at build time.

The concrete problem it solves is tool sprawl between project management and customer feedback. Teams that run a project management tool and a separate feedback tool duplicate work, publish stale updates, and leave users ignorant of what is happening to their requests. Sayr replaces that pair with a single system: tasks, comments, labels, and timeline entries each carry their own public or private toggle, and changes to that toggle take effect immediately.

Key capabilities

• Task management across five statuses (Backlog, Todo, In Progress, Done, Canceled) and five priority levels (Urgent, High, Medium, Low, None), with multiple assignees, subtasks one level deep, and relations typed as Blocks, Depends on, or Related to.
• A per-item visibility system that applies to tasks, comments (public versus internal), labels, and timeline entries, with labels carrying their own visibility settings.
• A public portal per organization with a live board sortable by Most Popular, Newest, or Trending, real-time voting counts, public task submission by signed-in visitors, reactions on public comments, and a member badge marking official responses.
• GitHub integration through a GitHub App, with bidirectional task-to-issue sync per repository and optional scoping by category, commit and pull request keyword references (Ref #N, Fixes #N, Closes #N, Resolves #N), commit and PR lifecycle entries on the task timeline, and comment syncing.
• Releases as milestones with progress charts, assignee workload and priority distribution, plus saved views, issue templates that pre-fill title, description, labels, assignees, category, priority, status, release, and visibility, and a full audit timeline.
• Real-time collaboration over WebSocket for all create, update, and delete events, with a ProseKit rich text editor, @mentions, threaded comments, edit history, emoji reactions, notifications, an inbox, and a cross-organization My Tasks view.
• A REST API with an OpenAPI spec served through Scalar, bearer token authentication, and rate limits of 100 requests per minute authenticated and 10 requests per minute unauthenticated.

Who uses it and how

• Product teams that publish a roadmap use the public portal to collect submissions and votes while keeping planning, internal comments, and private tasks out of the public view.
• Engineering organizations route work to GitHub by category, so a task in a given category syncs to the matching repository while activity in private repositories stays internal.
• Teams that must own their data self-host the Community edition from a Docker image, serve the portal on their own domain, and rely on GitHub OAuth, email and password login, TOTP two-factor authentication with backup codes, passkeys via WebAuthn, and per-session revocation.
• Larger organizations model people as members and teams with permission controls grouped under Organization, Content Settings, Tasks, and Moderation, resolved with a "most permissive wins" rule, alongside a blocked users list.

Getting started

Deploy the Community edition from its Docker image for free self-hosting, or sign up for the hosted Cloud edition at sayr.io. Note that Docker images are edition-locked at build time, so the edition is fixed when the image is built.

How it compares

No paid products or comparable tools are named alongside Sayr in the facts available for this entry, so it stands alone in this registry on that count. What can be said is that the hosted Cloud edition and the self-hosted Community and Enterprise editions share a codebase, which lets an operator move between hosting models rather than being confined to a vendor-run service.

When to use it — and when not to

Pick Sayr when a public roadmap and an internal board need to be one system, and when self-hosting is a requirement rather than a preference. Be cautious if licence certainty matters: the registry records the licence as NOASSERTION, and the project describes itself as source-available rather than open source, so a legal review is warranted before adoption. The facts supplied also omit operational prerequisites such as database, storage, or mail requirements, and the README excerpt ends mid-table, so a prospective self-hoster cannot confirm the running costs and dependencies from that material alone; with 57 open issues against 24 stars and 1 fork, the project also has a small community, which means support largely rests on the maintainers.

sayr/
├── apps/
│   ├── backend/          # Hono API server (Bun runtime, port 5468)
│   ├── marketing/        # Astro marketing site + Starlight docs (port 3001)
│   ├── nginx/            # Nginx reverse-proxy config
│   ├── start/            # TanStack Start frontend (port 3000)
│   ├── traefik/          # Traefik TLS termination config
│   └── worker/           # Background job processor (GitHub webhooks, cron)
└── packages/
    ├── auth/             # Better Auth configuration
    ├── database/         # Drizzle ORM schemas and CRUD functions
    ├── edition/          # Edition detection, capabilities, and plan limits
    ├── opentelemetry/    # Tracing and observability utilities
    ├── queue/            # Job queue abstraction (Redis or file-based)
    ├── storage/          # MinIO/S3 client with obfuscated filenames
    ├── ui/               # Shared Shadcn/ui component library
    ├── util/             # Shared utilities (slugs, date formatting, CDN URLs)
    └── typescript-config/# Shared TypeScript configurations

pnpm create-integration <integration-name> -a <author-name> -d <integration-description>