Event-driven automation & policy platform for fintech and business flows

A self-hosted alternative to Stripe + Zapier, focused on finance + operations.

Everything in Sapliy reduces to 4 core concepts:

graph TD
subgraph Organization["🔑 Organization"]
direction TB
subgraph ZoneProd["🧩 Zone: Production"]
direction TB
P_Events[⚡ Events]
P_Flows[🔄 Flows]
P_Events --> P_Flows
end
subgraph ZoneStaging["🧩 Zone: Staging"]
direction TB
S_Events[🧪 Events]
S_Flows[🔄 Flows]
S_Events --> S_Flows
end
end
subgraph FlowEngine["⚙️ Execution Engine"]
Logic{Logic & Rules}
Approval[👤 Approval]
Audit[📝 Audit]
end
subgraph Outputs["📤 Actions & Ledger"]
Ledger[(💰 Ledger)]
Webhook[🌐 Webhook]
Notify[✉️ Notify]
end
P_Flows --> Logic
S_Flows --> Logic
Logic --> Approval
Approval --> Audit
Audit --> Webhook
Audit --> Notify
Audit --> Ledger
classDef zone fill:#f9f9f9,stroke:#333,stroke-width:1px;
class ZoneProd,ZoneStaging zone;

• Owns everything
• Has users, teams, policies
• Root of all access control

The key abstraction. A zone is an isolated automation space combining:

• sapliy_secret_key (server-side)
• sapliy_publishable_key (client-side)
• Mode: test | live
• Flows, Events, Logs

Think: Stripe Account + Webhook Endpoint combined

Everything is an event:

• From SDK (sapliy.emit("checkout.clicked", {...}))
• From UI interactions
• From external providers (Stripe, payment gateways)
• From the gateway itself

No event → nothing happens.

Flows listen to:

• Event type
• Zone

Then execute:

• Logic (conditions, filters, approvals)
• Actions (webhooks, notifications, audit logs)
• Policy checks

This is the core value proposition.

graph TB
subgraph "Developer Experience"
SDK[SDK: Node/Go/Python]
CLI[Sapliy CLI]
UI[Fintech UI Components]
end
subgraph "Automation Layer"
FlowBuilder[Flow Builder UI]
end
subgraph "Core Platform - fintech-ecosystem"
Gateway[API Gateway :8080]
Auth[Auth Service :8081]
Payments[Payments :8082]
Ledger[Ledger :8083]
Zones[Zone Manager]
FlowEngine[Flow Engine]
Events[Event Bus]
end
subgraph "Infrastructure"
PG[(PostgreSQL)]
Kafka[(Kafka/Redpanda)]
Redis[(Redis)]
RMQ[(RabbitMQ)]
end
SDK --> Gateway
CLI --> Gateway
UI --> Gateway
FlowBuilder --> Gateway
Gateway --> Auth
Gateway --> Zones
Gateway --> Payments
Gateway --> Ledger
Payments --> Events
Events --> FlowEngine
FlowEngine --> Kafka
FlowEngine --> RMQ
Auth --> PG
Payments --> PG
Ledger --> PG
Zones --> PG

Every zone operates in two modes with separate isolation:

This reduces fear for companies to experiment without risking production.

All webhooks include:

• Signature header: HMAC-SHA256
• Event ID: Idempotency
• Zone ID: Context
• Timestamp: Replay protection

POST /webhook HTTP/1.1X-Sapliy-Signature: sha256=abc123...X-Sapliy-Event-ID: evt_123X-Sapliy-Zone-ID: zone_456X-Sapliy-Timestamp: 1706972400

Keys can be scoped to specific operations:

• events:emit — Send events
• flows:read — View flows
• flows:write — Create/edit flows
• admin:* — Full access

- "Who can create zones" → Admin only
- "Who can deploy live flows" → Admin + Finance

{
"allow": ["flow.deploy"],
"when": { "role": "admin" }
}

OPA-style policy language for complex rules.

Revenue drivers:

• Zone count
• Event volume
• Notifications (WhatsApp, SMS)
• Third-party plugins
• Hosted execution
• SLA guarantees

1. Run the ecosystem: docker-compose up -d in fintech-ecosystem
2. Create a zone: Use the API or Flow Builder UI
3. Install SDK: npm install @sapliyio/fintech
4. Emit events: sapliy.emit("checkout.completed", { amount: 100 })
5. Build flows: Use the Flow Builder to react to events

• fintech-ecosystem — Core backend services
• fintech-sdk-node — Node.js SDK
• fintech-sdk-go — Go SDK
• fintech-sdk-python — Python SDK
• fintech-ui — React components
• fintech-automation — Flow Builder UI
• sapliy-cli — Developer CLI
• fintech-docs — Documentation site

MIT © Sapliy