Agreement Infrastructure for Developers
Data-first, not document-centric. Your structured business data drives every document, every workflow, every signing decision — not the other way around.
Think Terraform for agreements. Define it all as code in your repo. Deploy with a CLI. Run via API — version-controlled, declarative, and built on open primitives.
Describe it in plain English — we'll draft the document, its signature fields, and the signing order.
Infrastructure as Code
Define Your Workflow as YAML
No more managing templates in a dashboard and stitching together REST calls. Your entire signing workflow lives in your repo — validate, preview, and run locally. When you're happy, push to deploy.
apiVersion: signstack/v1beta2
kind: Blueprint
metadata:
key: client_contract
version: 1.0.0
spec:
inputs:
- key: client
schema: client@1.0.0
- key: deal
schema: deal@1.0.0
participants: # Resolved dynamically from entity data
- key: client_signer
name: { expression: "$.client.name" }
email: { expression: "$.client.email" }
- key: account_exec
name: { expression: "$.deal.accountExec.name" }
email: { expression: "$.deal.accountExec.email" }
envelopes:
- key: contract_envelope
documents:
- template: service_agreement@1.0.0
- template: enterprise_addendum@1.0.0
includeIf: "$.client.tier = 'Enterprise'" # Conditional doc
orchestration:
key: root
type: group
execution: sequential
children:
- key: internal_review # Parallel approval gate
type: group
execution: parallel
children:
- key: legal_review
includeIf: "$.deal.value > 50000" # Only for large deals
type: participant
participant: legal
action: { type: sign, envelope: contract_envelope }
- key: finance_review
type: participant
participant: finance
action: { type: sign, envelope: contract_envelope }
- key: client_signs # After internal approval
type: participant
participant: client_signer
action: { type: sign, envelope: contract_envelope }Same primitives, your choice — drive everything from the terminal, or design visually in Studio.
How It Works
Build in Minutes, Not Months
Go from idea to a fully automated, legally-binding workflow in three simple steps.
Define as YAML
Write your schemas, templates, and blueprints as declarative YAML files. Version them in Git. Validate locally with the CLI.
Test Locally
Validate schemas, preview rendered documents, and run full workflows on your machine — no deployment needed. Iterate until everything looks right.
Deploy & Integrate
signstack push to deploy. Your app code becomes a single API call — pass a blueprint key and entity data. Webhooks keep your system in sync as steps complete.
Why SignStack
More Than an API. It's a Complete Engine.
Built on powerful, unopinionated primitives — JSON Schema, JSONata, and a recursive step tree. You define every rule. We execute it.
Version-Controlled
Every schema, template, and workflow is a YAML file in your repo. Review changes in PRs. Roll back with git revert. Deploy through your existing CI/CD pipeline. No more dashboard drift.
Complex Orchestration
A recursive step tree you fully control — sequential, parallel, quorum, conditional. Every branch, every gate, every routing decision is a JSONata expression over your business data. If you can describe the workflow, you can declare it.
Legally Compliant
ESIGN & UETA compliant e-signatures with complete audit trails. SHA-256 tamper-evidence, consent capture, and detailed event logging for full legal defensibility.
AI-Native
Describe a workflow in plain English. Get working YAML. Declarative definitions mean AI generates the entire workflow — schemas, templates, orchestration — not just integration code.
Ready to Build the Future of Agreements?
Stop wrestling with rigid, document-centric platforms. Start building the intelligent, data-driven agreement workflows your users deserve.