A hierarchy that scales
Organizations hold workspaces; workspaces hold spaces; spaces hold projects; projects hold work items. Roles and workflows inherit down — no plugins required.
- Personal or Org
- Scrum · Kanban · Hybrid
- Roles at every level
Fairlx is the agile work OS for modern teams — boards, sprints, workflows, docs, and analytics in one hierarchy. With Fairlx+, assign bugs to autonomous agents that code in isolated Azure sandboxes, boot live previews, and open pull requests.

Works with the tools your team already ships in
Three decisions shaped the product: a hierarchy that scales without plugins, an agent that takes a work item to a reviewed PR, and one runtime you can run from Slack, Cursor, or GitHub.
Organizations hold workspaces; workspaces hold spaces; spaces hold projects; projects hold work items. Roles and workflows inherit down — no plugins required.
Sidebar overflows at 390px
Assigned to @Fairlx
Fairlx+
Working
fix(nav): prevent 390px clip
Opened as you · fairlx/WEB-12
Assign a work item to @Fairlx. It reads the ticket, posts a plan you Accept, boots an isolated Azure sandbox, and opens the PR under your GitHub identity — not a chatbot in a sidebar.
#eng-web
@Fairlx fix WEB-12
sandbox healthy
MCP · fairlx
> plan sprint
3 tools called
fairlx_start_session
PR #412
fairlx/WEB-12
+24 -8
WEB-12
In Progress → Review
status auto-advanced
The same agent answers in Slack, Discord, Teams, and WhatsApp, exposes itself to Cursor via MCP, and shows up on the pull request. One session — wherever the team already works.
Fairlx+ cuts a branch, runs the sandbox, and opens the PR under your identity. Click a station to pin it.
No marketplace plugins to assemble. Boards, backlog, timeline, workflows, docs and analytics share one data model, so a change in one shows up everywhere
Kanban, Scrum or Hybrid per project. WIP limits with visible warnings, swimlanes by epic or assignee, and cards that show exactly the fields you choose.

AI teammates you can give real work to. Bots can sign in to your tools, use them just like you do, and come back with finished work.
Launch new dashboard
Hey team, let's get the new project dashboard launched this week! Can we organize the tasks and get it ready?
On it! I've organized the sprint tasks on our Kanban board:
• @Sam — Build analytics & stats widgets
• @Alex — Test layout on desktop & mobile
• @Annie — Write user guide & help tips
Moved project to In Progress on the board. @Sam, you're up first!
Finished building the new analytics cards and charts! Everything loads instantly and is fully responsive.
Moved my card to In Review on the board. @Alex ready for your check!
Not a chatbot in a sidebar. Fairlx+ takes a work item from your board to a reviewed PR — with a plan you approve, an isolated sandbox, and a preview you can click.
Assign a work item to @Fairlx. It reads the ticket context, comments, and repository files, then posts a clear implementation plan. Once you click Accept, it provisions an isolated Azure container — git and shell never touch the Fairlx host.

The live preview mounts only after automated container health-checks return 200 OK. Review code changes side-by-side, watch test suites run in real time, and let the agent auto-fix failing tests before review.

The pull request opens directly from the sandbox under your verified GitHub identity — never an anonymous workspace bot. Interact with @Fairlx directly in Slack, Discord, Teams, WhatsApp, or operate it inside Cursor via MCP.

Streamline code reviews with clear diffs, better context, and fewer back-and-forth comments. Keep PRs moving without leaving Fairlx.
Assign a work item, Accept the plan, and Fairlx boots a dedicated Azure VM. Git, shell, and the agent stay inside it — one live sandbox per person per project.
Git, shell, and the coding agent execute only inside an isolated Azure VM. The host never sees the workspace disk.
One sandbox per user per project. Ten teammates get ten VMs — you never inherit someone else’s workspace.
Idle boxes suspend in memory (disk kept, CPU billed off), then auto-delete after 30 minutes so leftover storage cannot sit.
Create → clone → install → start. The preview iframe mounts only after the container health-check returns 200.
Project secrets are names-only in the UI and injected at session start. Values never come back through tools or logs.
Compile and test failures are patched in place. Fairlx does not reboot or destroy the VM — uncommitted work stays.
Fairlx compiles triggers, sandboxes, and verification into a single continuous loop. When a test fails in the container, the agent diagnoses the trace, rewrites the code, and re-runs the suite until it passes.
The agent detects the failure, diagnoses the stack trace, writes a fix, and re-runs the suite. If tests still fail, it loops back — refining the patch until every test is green.
Workflow run #418 · commit a91f0c
CI webhook detected failing viewport test in NavBar.test.tsx and assigned an autonomous sandbox.
Test fails
← GitHub Actions CICI detects 2 failing tests in NavBar.test.tsx
Agent investigates
← Fairlx Diagnostic EngineReads stack trace, identifies root cause in CSS overflow
Writes a patch
← AST Code GeneratorApplies clamp() fix to sidebar width calculation
Tests still failing
← Vitest Runner1 edge case remains — sub-400px viewport overflow
Agent refines fix
← Self-Healing RefinerAdds overflow-y-auto + clamps min-width on sidebar
All tests pass
← Test Verification Suite14/14 green — zero regressions
PR opened
← GitHub Pull Request APISigned commit, linked to WEB-12, preview deployed
Autonomous loop executing
Step 1 of 7·Test fails
When tests fail in the sandbox, the agent parses the stack trace, applies a refined AST patch, and re-runs the suite until 100% green. Zero human intervention for mechanical breakages.
Agents write inside ephemeral Azure Container Apps with zero host filesystem access. Production codebases stay untouched while live previews let your team test instantly.
Every pull request requires verified commit signatures and supervisor approval before main branch merges. Trigger directly via Slack, Discord, Linear, or MCP.
Fairlx doesn't ask your team to live in another tab. The same runtime answers in the thread, exposes itself to your IDE, and shows up on the PR.

@Fairlxfix WEB-12 — sidebar overflows on mobile screen
Resuming session for WEB-12 in Azure sandbox.
@Fairlx in Slack, Discord, Teams, or WhatsApp starts or resumes the session bound to a work item. Slash commands create bugs, stories, and tasks directly from the thread.
Cursor, Claude, or Codex operate Fairlx through ~100 fairlx_* tools — plan sprints, move items, start sessions. Fairlx calls your MCP servers back: Sentry, Datadog, or any HTTP server.
fix(nav): prevent mobile viewport clipping #412
Link a repo to the project. Commits, branches, and pull requests bind to the item, PRs open under your identity, and merges automatically move the item along your workflow.
Fairlx turns you into a 10x team. Drop in your specs, assign work to people or AI, let top models code in isolated cloud sandboxes, and launch with live interactive previews.

Drop in any document — a product spec (PRD), a feature document (FRD), or rough notes. Fairlx extracts every detail so the AI understands what needs to be built.
Product Requirements · What users need & expect
Functional Requirements · How the system should work
Figma Design Spec · Visual layout & design tokens
Built with enterprise needs in mind while staying simple enough for a two-person studio. No tiers, no gated features.
Billing usage chart on workspace home
Show traffic, storage and compute for the current month with the threshold line.

16 types · space scoped
Text, number, date, select, user, currency, percentage, URL, labels — scoped to workspace, space or project, with defaults and validation.
Priya Raman
Web Platform
Log hours per work item, compare estimates to actuals, and export a weekly timesheet per person.
Billing v2 — Product PRD
PRD · 84 KB
Usage aggregation engine spec
Tech Spec · 126 KB

Public REST & MCP work items
API Doc · 61 KB
Release notes v2.8
Release · 240 KB
14 document categories from PRD to release notes, version history, tags, and 5 GB per project.
Work Items
Sprints
Members & Teams
Documents
Organization, workspace, space, team and project roles — plus custom roles stored in the database. Guards run server-side.
Web Platform
8 members · Lead Priya Raman
Board, sprints, deployments and analytics for the web app.
ATPayments & Ledger
5 members · Lead Sara Chen
Approvals, Stripe webhooks, and ledger integrity.
Teams with leads and granular permissions. Programs group teams for portfolio-level analytics.
Fairlx+ opened PR #412 for WEB-12
2 minutes ago
Sara requested your approval on WEB-30
25 minutes ago

Marcus mentioned you in WEB-21
1 hour ago
Aiko adjusted due date on WEB-24
3 hours ago
Ten event types delivered in-app, by email or webhook — assignments, approvals, mentions, due dates, PRs.