In Progress

OrgDocs — Automatic Salesforce Org Documentation

SaaS that connects to a Salesforce org via OAuth, extracts metadata (Apex, Flows, Objects, Profiles, Permission Sets) and automatically generates structured documentation exportable as PDF, Markdown, HTML, Notion and Confluence.

Context

OrgDocs is a SaaS built for Salesforce admins and developers who spend hours manually documenting their orgs. The tool connects via OAuth, automatically extracts critical metadata (custom objects, Flows, Apex classes, Profiles, Permission Sets) and generates structured, exportable documentation — eliminating a time-consuming, low-value task.

Scope & Objectives

5 extractors: Objects & Fields, Flows & Process Builder, Apex Classes & Triggers, Profiles, Permission Sets
5 renderers: PDF, Markdown, HTML, Notion (API), Confluence (API)
Salesforce OAuth 2.0 authentication — Connected App, no CRM data stored
Async architecture: Heroku Eco Dyno Worker for long-running extraction jobs
Quota management and billing via Stripe — freemium model

Technical Architecture

Next.js / Vercel — Frontend and API routes
Heroku Eco Dyno Worker — Asynchronous extraction jobs
Supabase — Database and authentication
Upstash Redis — Job queue and cache
Cloudflare R2 — Generated document storage
Claude API — Documentation enrichment and summarization
Stripe — Subscriptions and quota management

Stack & Technologies

Next.js 15 + TypeScript — SaaS frontend
Supabase (Postgres + Auth) — Persistence and users
Heroku Worker (Node.js) — Async processing
Upstash Redis — BullMQ queue and session cache
Cloudflare R2 — Document storage (PDF, MD, HTML)
Salesforce REST API + Metadata API — Metadata extraction
Claude API (Anthropic) — AI documentation enrichment
Stripe — Billing, subscriptions, webhooks

Roadmap

1
Phase 0 — Architecture
Data schema definition, Heroku Worker async architecture, Salesforce Connected App OAuth setup, Supabase + R2 infrastructure.
2
Phase 1 — Extractors ← Active
Implementation of the 5 Salesforce metadata extractors: Objects, Flows, Apex, Profiles, Permission Sets. 35 tickets defined.
3
Phase 2 — Renderers
Generation of 5 output formats: PDF (Puppeteer), Markdown, HTML, Notion API push, Confluence API push.
4
Phase 3 — SaaS & Billing
Full user interface, dashboard, quota management, Stripe integration and production deployment.

Progress

Tickets defined

4 structured phases

Extractors

Objects, Flows, Apex, Profiles, PermSets

Renderers

PDF, MD, HTML, Notion, Confluence

Phase 1

Active phase

Extractors in development