Roadmap
Where Opsly is going
Opsly is built by one person in the open. This page is the honest state of the work: what already ships, what's actively being built, and what's still an open question. There are no dates here on purpose: a date I can't keep is worse than no date at all.
Shipped and in the current build Major workstreams, tracked as epics Smaller improvements and fixes
Shipped
14Available in the current build. Run it today and it's there.
-
Projects, tasks & Kanban
Priorities, assignees, full history, board and dashboard views.
-
Organizations & RBAC
Multi-tenant orgs with per-role permissions.
-
Offline-first sync
Edits queue locally and sync on reconnect.
-
Eight languages
English, Spanish, French, German, Portuguese, Japanese, Chinese, Arabic.
-
Real-time updates
Notifications and cross-org changes stream over Server-Sent Events.
-
Markdown & Mermaid
Rich editor with diagram rendering across notes, tasks, and projects.
-
Audit trail
A record of changes across tasks and organizations.
-
Data export
Full JSON/CSV export of tasks, projects, comments, and notes, permanently ungated.
-
Dependency trees
Model and enforce relationships between tasks.
-
Custom fields & statuses
Typed fields and custom workflow stages with colors.
-
SLA tracking
Response and resolution policies per priority, with at-risk warnings.
-
Webhooks
Inbound and outbound real-time events with external systems.
-
Scoped API keys
Machine credentials with granular permission scopes.
-
Per-org branding
Custom primary color and logo per organization.
Major workstreams
10Tracked as epics on GitHub, each broken into sub-issues. Listed by issue number, not priority.
-
File attachments
S3-backed files attached to tasks, projects, and notes, not just exports. Storage layer first, then per-entity linking and UI.
-
Hosted-tier billing and limits
A billing sub-module for the hosted version. Self-hosting stays unrestricted.
-
App at /app, plus this site
Move the hosted app to its own base route and stand up an informational site with product overview, pricing, and docs.
-
Full UI test suite
Playwright coverage of layouts and functionality, paired with a UAT document and stress testing.
-
Org-customizable categories & statuses
Make categories and statuses org-customizable the way stages already are, with permission and terminology gates. Inbound webhooks must accept the custom values.
-
Feature toggles apply instantly
Disabling a feature should take effect everywhere at once, with no stale API calls or empty dropdowns. The core app must work with every optional feature off.
-
Granular permissions
Split read from write, and split member management from role and permission administration.
-
Direct messaging
Message other users within the same instance and org.
-
Two-factor authentication
Per-user 2FA, with org admins able to require it for all members.
-
In-app user documentation
Docs that live inside the app, covering webhooks, permissions, and the rest with worked examples.
Improvements & fixes
44Smaller open items, grouped by theme. Every one is a public issue you can read, comment on, or pick up.
-
Localization & terminology
Audit-log descriptions, notification toasts, and org-settings copy that still bypass translation or per-org terminology.
-
Interface state that sticks
Remembering the last settings tab, the active project tab, and the selected SLA window across refreshes.
-
Notifications & digests
Real-time delivery, per-channel toggles for in-app versus email, and
List-Unsubscribeheaders on digest mail. -
Webhook reliability
Firing outbound hooks on SLA breaches and warnings, plus fallback values and clearer permission-aware setup guidance.
-
Notes & editing
Folders for organization, live co-editing sync, and reference chips rendered in previews.
-
Accounts & access
Self-service password reset for local auth, and marking users inactive so history survives revoked access.
-
Offline resilience
Capping offline-queue growth when the backend is unreachable and showing a clear indicator of pending syncs across the UI.
-
Testing & CI
Stress and scale testing, a user-acceptance document, lint checks in CI, and a dead-code sweep.
Something missing?
The roadmap is shaped by what people actually need. If something you'd rely on isn't here, say so. Feature requests start as an issue, and the contributing guide asks for one before any code anyway.