One canonical Work Item
Epics, stories, tasks, bugs, service requests and change requests are one record. Backlog, list, board, search and counts are views of it, so they cannot disagree. Available now.
Delivery control plane for software teams
One record of delivery for your team, your clients and your AI Agents.
ProjectHubs keeps one canonical record of delivery work for a Team's projects. Staff plan and deliver, clients see an allowlisted view of their own project, and AI Agents do delegated work without ever acquiring the human authority to approve, merge, deploy or close.
Pre-release
One canonical Work Item
Agents never approve or merge
Client portal rebuild · board view
Illustrative
Backlog
Export invoices as CSV
Fix date filter on reports
In progress
Sign-in page redesign
Awaiting approval
Specification for audit export
Human approval
Done
Password reset emails
Illustrative board, not live data. Agent specifications and approval gates are in development.
Why teams use it
One record, and authority that matches the role
Project truth fragments across tickets, chat, schedules and Git. Health becomes easy to overstate, client decisions lose their trail, and Agent work leaves no record a person can approve. ProjectHubs keeps one record and gives each participant only the authority their role justifies.
Clients see an allowlist
Clients see only what is explicitly shared with them: never internal notes, rates, costs, capacity, security findings or raw Agent prompts. The client workspace is in development.
Agents with bounded authority
An Agent's rights are the intersection of its human sponsor's rights, its capability grant, the project and the exact human approval. It cannot approve, merge, deploy or close. In development.
How Agents connect
Your Agent client, a typed protocol, human approval
Agents run in your own agent client, on your machine or in your CI. They reach ProjectHubs through the projecthubs CLI or the TypeScript Agent SDK. The server decides what may happen next; ProjectHubs runs no model, holds no model key and never merges or deploys.
$ projecthubs capability
what this Agent's capability grant allows
$ projecthubs work-item next WEB-44
allowed next actions, decided by the server
$ projecthubs approval request … --gate spec
→ stops here until a person approves the exact revision
Where it stands today
Teams, projects and Work Items
Accounts, Teams, billing and audit foundations; projects with accountable membership; the canonical Work Item with backlog, list and board views.
Clients and governed Agents
The client workspace, requests and decisions, planning and health, reports, Agent planning and execution with human approval gates, evidence review and schedule.
A runtime or a Jira clone
ProjectHubs does not run Agents or models, does not merge or deploy, does not score individual performance and is not a workflow designer.
Start with one project
ProjectHubs is pre-release. Create a Team, set up a project and plan from one record, or talk to us about delegating work to Agents.