Skip to main content
Pharen Hub is an AI workspace for teams that want less tool chaos and more shared context. It brings docs, lists, communication, workflows, approvals, and AI agents into one place. Not as another tab next to your existing stack, but as a workspace where people and agents can work from the same source of truth.

​
What you can do here

This documentation helps you understand the product, set up a workspace, and build with Pharen without guessing where things belong.

Understand the workspace

Learn the core ideas behind workspaces, docs, lists, workflows, approvals, and agents.

Run it locally

Set up the development repo, run quality checks, and contribute changes without fighting the toolchain.

Explore Hub modules

See how docs, lists, channels, mail, workflows, and AI agents fit together in the product.

Use the API

Authenticate, create pages, update resources, and connect Pharen with your own systems.

​
The short version

Most teams already have enough software. They write in docs, plan in tasks, talk in chat, store process data in spreadsheets, approve work in email, and ask AI in a separate window. The work happens between those tools, so the context gets lost. Pharen Hub is built around a different idea:
AI becomes useful when it can work inside the same context as the team.
That means an agent can read the right document, inspect a list record, trigger a workflow, request approval, and leave a clear trace for the team. It also means humans stay in control. Agents prepare, route, summarize, and execute work, but approvals and permissions remain part of the system.

​
Where to start

If you are new to Pharen, start with these pages:
1

Read the core concepts

Start with Core concepts to understand the language used across the docs.
2

Set up a workspace

Use the Quickstart if you want to try the hosted product with a real workspace.
3

Set up local development

Use Local setup if you are contributing to the product or working with the monorepo.
4

Go deeper into a module

Jump into Workflows, Lists, Studio, or AI Agents once you know what you want to build.

​
A note on tone

Pharen is not documented as a generic SaaS dashboard. The product is opinionated: context matters, agents need guardrails, and work should not be scattered across five disconnected tools. The docs follow that same line. They should be practical, clear, and human. If a page does not help someone make a real decision or complete a real task, it needs to be tightened.