DriveDesk Core review

Review the backend/platform proof in 10 minutes.

DriveDesk Core is my public proof for the larger DriveDesk direction: FastAPI/PostgreSQL backend structure, tenant and RBAC boundaries, audit/outbox, workflow rules, adapter contracts, OpenAPI, CI, docs, public demo, and public-safe recovery evidence.

Open GitHub repo Open public demo Latest CI proof Send a workflow
HTTP 200Public demo checked on 2026-06-18.
CI successRun 27750351716 on main.
Pages successRun 27750347913 deployed the demo.
Scheduled validationRun 27750439490 passed.

Backend Shape

FastAPI, PostgreSQL, Alembic, tenants, memberships, RBAC, current-user lookup, token/session boundaries, tenant-owned records, and OpenAPI contracts.

FastAPIPostgreSQLOpenAPI

Workflow Layer

Business records, lifecycle transitions, workflow rules, task creation, adapter sync requests, audit events, outbox handoff, and operator-visible status.

WorkflowAuditOutbox

Integration Layer

Adapter catalog, mapping validation, transforms, connection scopes, operation contracts, accounting export, diagnostics, reconciliation, and incident runbooks.

AdaptersCRM/ERPRunbooks

DevOps Evidence

Docker Compose runtime, pytest coverage, CI, public demo checks, scheduled validation, backup/restore drill, rollback drill, SLO canary gate, Helm/OpenTofu/GitOps evidence.

DockerCIRecovery

Reviewer Surface

The repo is public, the demo is reachable, the README has a reviewer path, and the proof is inspectable through code, docs, Actions, scripts, and generated OpenAPI artifacts.

DocsDemoActions

Business Fit

This is the strongest public anchor for backend/platform, internal tools, CRM/ERP/API integrations, operations automation, and remote-first delivery conversations.

PlatformIntegrationsRemote

10-Minute Review Path

  1. Open the public demo and scan workflow/integration screens.
  2. Open the GitHub repo and README reviewer path.
  3. Check latest CI, Pages deploy, and scheduled validation.
  4. Open OpenAPI and one docs path: system design, operation contracts, or outbox recovery.
  5. Use the result to decide whether to send a role, workflow, or technical problem.

Role Match

  • Backend engineer: FastAPI/PostgreSQL, OpenAPI, tests, auth/session boundaries, tenant-owned records.
  • Platform engineer: tenants, RBAC, audit/outbox, workers, docs, CI, release and validation paths.
  • Integration engineer: adapter catalog, mapping/transform boundaries, scopes, diagnostics, reconciliation, incident runbooks.
  • DevOps/recovery: scheduled validation, backup/restore, rollback, SLO gate, GitOps/OpenTofu/Helm evidence.

Best First Message

Send one messy workflow, the systems involved, one success condition, and whether you need a role hire, fixed-scope build, technical review, or recovery sprint.

Start conversation