Workspace
How work moves through Homany - capture, organize, monitor, act.
Workspace is the storyboard your team actually works in: intake drops into the same surface your delivery managers plan from, monitoring sits next to the data sponsors review, and agents act on the work without leaving the boundary.
- One permission model across sheets, Gantt, Kanban, dashboards, forms, and reporting.
- Agents act inline on tasks, approvals, and reports.
- Same surface in your cloud, our managed region, or on-premise.
The six surfaces
Everything your team needs, in one workflow.
Forms capture the work, sheets, Gantt, and Kanban organize it, and dashboards and reporting keep everyone looking at the same numbers - under one permission model.
- Capture
Forms
Structured intake so requests arrive as typed work - fewer dropped handoffs from email and chat.
- Organize
Sheets
The grid planners live in - bulk edits, formulas, and row-level permissions over a single source of truth.
- Organize
Gantt
Dependencies, baselines, and critical path that give delivery clear execution visibility.
- Organize
Kanban
Swimlanes and WIP limits so execution flows with less day-to-day coordination overhead.
- Monitor
Dashboards
Live portfolio read-outs sponsors trust - fewer status meetings, no warehouse copy.
- Monitor
Reporting
Scheduled, finance-grade exports that reconcile against ERP and billing for clean handoffs.
1 · Capture
Intake that lands inside the same surface delivery already lives in.
Requests, approvals, and ideas arrive through forms and inboxes that drop straight into the sheets, boards, and Gantt views your team executes from. No re-keying, no parallel intake tool.
- 1capture intake
- 2submit form
Intake arrives as structured fields, not free-text email.Illustrative
A schematic preview of the intake surface - final screenshots land closer to launch.
2 · Organize
Sheets, Gantt, and Kanban - over one source of truth.
Planners stay in sheets, delivery managers stay in Gantt, executors stay in Kanban. They are not separate tools synced via integrations - they are views over the same records, with the same permissions.
Sheets
Bulk editing, formulas, row-level permissions, and an audit-ready change history.
Gantt
Dependencies, baselines, and critical path that stay in sync with the underlying sheet.
Kanban
Swimlanes, WIP limits, and policy gates that respect role-based access.
Folders & portfolios
Nest projects under portfolios, programs, and clients without losing roll-up reporting.
Docs in context
Specs, briefs, and decisions live next to the work they describe - versioned and search-indexed.
Roles & access
Internal teams, external collaborators, and agents share one permission model - no shadow access.
- 1move card
- 2update status
Move a card and its status, owner, and timeline update everywhere at once.Illustrative
Schematic Kanban preview - the same records also render as a sheet and a Gantt timeline.
3 · Monitor
Dashboards and reports sponsors actually trust.
Live dashboards for delivery, scheduled reports for finance, and ad-hoc views for sponsors - all built from the same workspace data, no warehouse copy required.
- 1monitor dashboard
- 2drag timeline
Sponsors watch the same numbers delivery is working from.Illustrative
Schematic dashboard preview - live tiles and charts refresh as work happens.
4 · Act
Agents act on the work - they don't just talk about it.
Agents pick up tasks, draft updates, run approvals, and post reports inline. Every action is scoped, logged, and reversible - and they only escalate to humans when your playbook says they should.
- Agents own tasks
- Assign agents to tickets, intake items, or approval queues - they execute under named roles and budgets.
- Playbook-driven handoffs
- Define when an agent acts alone, when it asks a human, and when it escalates to a named approver.
- Audit and reverse
- Every action is logged with input, output, and reasoning. Roll back at the workflow or task level.
- BYOK and budgets
- Bring your own model keys; cap token spend per team and per agent from the admin console.
What it does inside Workspace
- Cleans up and reorganizes boards
- Updates task statuses and owners
- Drafts status summaries and reports
- Runs first-pass approvals to a named human
Every action is scoped, logged, and reversible - agents escalate to a named human whenever your playbook calls for judgement.
Agent-first
The surface agents act on
The workspace is where agents execute - within scope, with approvals and a trail.
- Product
Agents
How agents execute work within scope, with approvals and a full audit trail.
See agents - Guide
Agent-ready operations playbook
Structure work so agents can execute safely - guardrails and a staged rollout.
Read the guide - Docs
API & MCP overview
The operational surface agents and integrations act on, and how MCP fits in.
See the API
Try Workspace
Run a Workspace trial on a sovereign-ready cloud
Spin up a workspace in minutes, invite collaborators at no cost, and bring your own AI keys when you're ready to turn on agents.