DriveDesk Core review

Review the backend automation and integration proof in 10 minutes.

DriveDesk Core is my public evidence for the larger DriveDesk operating-system path: FastAPI/PostgreSQL backend structure, tenant and RBAC boundaries, audit/outbox, workflow rules, adapter contracts, business-intake API handoff, OpenAPI, CI, docs, public demo, and public-safe recovery evidence.

Open GitHub repo Open public demo Latest CI evidence Send a workflow
HTTP 200Public demo checked on 2026-07-03 UTC.
CI successRun 28679757049 on main.
Pages successRun 28679756530 deployed the demo.
Scheduled validationWorkflow active on main.
Demo healthWorkflow active on main.

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

Docker/CI Evidence

Docker Compose runtime, pytest coverage, CI, public demo checks, scheduled validation, health/smoke checks, backup notes, rollback notes, release-gate docs, and recovery handoff evidence.

DockerCIRecovery

Reviewer Surface

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

DocsDemoActions

Business Fit

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

BackendIntegrationsRemote

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 CI, Pages deploy, scheduled validation, and public demo health.
  4. Open the Business Intake API Handoff, 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.
  • Backend/internal-tools owner: tenants, RBAC, audit/outbox, workers, docs, CI, release notes, and validation paths.
  • Integration engineer: adapter catalog, mapping/transform boundaries, scopes, diagnostics, reconciliation, incident runbooks.
  • Docker/CI handoff: scheduled validation, health checks, backup notes, rollback notes, release gates, and recovery handoff evidence.

Fast Review Next Step

The strongest evaluation path is a real workflow or role scope with one clear success condition. I can map the business process, identify the integration and operational risks, build the first working slice, and leave verification evidence through tests, logs, docs, runbooks, and demo links.

Start conversation