Skip to main content
Fabric is designed to run on your infrastructure. This page covers local dev via Docker Compose and AWS deploy via Copilot. Both paths are first-class.

​
Local dev (Docker Compose)

1

Clone the repo

2

Configure secrets

Copy the example env file and fill in the values for the LLM and embedding provider:
Generate a strong ENCRYPTION_KEY with openssl rand -base64 32.
3

Start the stack

This starts Postgres (with pgvector + tsvector), Redis, the FastAPI API, a Celery worker, and the Vite frontend.
Verify with curl http://localhost:9000/healthz
4

Open Fabric

Visit http://localhost:5174. Sign up with any email; check the backend logs for the verification link if email isn’t configured.
5

Add your first connection

From the Connections page, click Add Connection and pick Gmail, Slack, Drive, Fireflies, IMAP, or a database.OAuth sources will redirect through the provider’s consent screen. Database sources take host/port/credentials directly.
6

Ask something cross-source

Open chat and try:
“Who sent emails about the billing migration this week, and what did they say in Slack?”
You should see tool calls for search_knowledge, follow_edges, and possibly query_database in the trace drawer.

​
Production deploy (AWS ECS Fargate)

Production deploys require AWS Copilot. Install with brew install aws/tap/copilot-cli.
1

Configure AWS

2

Initialize Copilot

Creates the Copilot app, environment, and service definitions. Takes ~5 minutes.
3

Push secrets to SSM

Reads your .env.staging file and pushes each value to AWS SSM Parameter Store as a SecureString. Secrets are injected into the container at start.
4

Deploy

Builds both the API and worker images, pushes to ECR, and updates the ECS services in parallel. ~4–5 minutes.
5

Wire DNS

Creates Route 53 records for api.fabric.yourdomain.com and fabric.yourdomain.com, provisions a CloudFront distribution, and deploys the SPA to S3.

​
What you get

API

api.fabric.yourdomain.com — FastAPI with 72+ endpoints.

Frontend

fabric.yourdomain.com — React SPA, served via CloudFront.

Swagger UI

/docs — interactive API playground.

ReDoc

/redoc — read-only reference.

​
Next steps

Connectors overview

All six sources plus database integration.

Architecture

How the pieces fit together.

Security

Multi-tenant isolation, credential storage, OAuth handling.

Observability

Langfuse traces, structured logs, cost accounting.