Hierarch Documentation
Hierarch is a task and project management application built for designers. It combines nonlinear design phases, rich artifact management, and deep integrations with the tools your team already uses.
Architecture →
Tech stack, database schema, authentication, and edge functions.
Core Features →
Design phases, tasks, projects, artifacts, and the focus timer.
Integrations →
Linear, Figma, Jira, and Slack. OAuth setup, scopes, and data flow.
API Reference →
Edge function endpoints, request formats, and authentication.
Quick Reference
| Stack | React 18 + TypeScript + Vite + Tailwind v4 |
| Backend | Supabase (Postgres, Auth, Storage, Edge Functions) |
| Edge Runtime | Hono on Deno (Supabase Edge Functions) |
| Hosting | Vercel |
| Auth | Supabase email/password and Google OAuth. OAuth 2.0 for third-party integrations. |
| Integrations | Linear, Figma, Jira, Slack |
For Integration Developers
If you are here to understand how Hierarch connects with external services for an OAuth application or API integration, start with the integration-specific pages:
- Linear . Issue sync, status management, design metadata, Figma attachment linking.
- Figma . File embedding, oEmbed thumbnails, design token access, dev resource linking.
- Jira . Issue sync via serverless proxy, OAuth 2.0 (3LO), REST API v3.
- Slack . Notifications, phase change alerts, feedback request routing.
Each integration page documents the required OAuth scopes, API endpoints, data Hierarch reads and writes, redirect URIs, and authentication flow.