I built this because most workflow + e-sign vendors force you into their UI and signatures.
My goal was to let developers embed document workflows directly into their own product — the API controls routing + lifecycle, and the developer fully owns the UX.
Some context:
I built this because most workflow + e-sign vendors force you into their UI and signatures. My goal was to let developers embed document workflows directly into their own product — the API controls routing + lifecycle, and the developer fully owns the UX.
Architecture highlights: • API Gateway → Lambda microservices (TS/Node) • Core services: workflow, documents, auth, webhooks • S3 (per-tenant isolation) + PostgreSQL (RDS) • Async document processing via SQS + processor workers • Redis planned for caching • Observability: CloudWatch + X-Ray • Developer portal w/ key management + playground • Webhooks supported; polling fallback
Happy to talk about trade-offs (e.g., multi-tenant isolation, async processing patterns, DX decisions, Lambda vs containers) or roadmap ideas.