Skip to main content
Flowker is a financial workflow orchestration platform created by Lerian Studio. It is designed to manage and automate complex transactional flows in multi-tenant environments, combining orchestration, integration, and security in a single, resilient system. Flowker helps financial institutions and partners coordinate the full lifecycle of a transaction. You can automate what happens before, during, and after the operation, including anti-fraud checks, payment routing, manual approvals, and customer onboarding.

Why use Flowker?


Financial systems need flexibility. Not every transaction follows the same rules or steps. Flowker gives you the tools to build and control your own authorization workflows, connect to external services, and make decisions based on real-time data while keeping everything auditable. At its core, Flowker relies on two main concepts:
  • Workflows: Define and orchestrate how tasks run across the system. You can organize them in sequence or parallel, store execution states, and recover them when needed.
  • Tasks: Represent the individual steps within a workflow, such as calling an API, triggering a plugin, validating data, or waiting for input.
Each result determines the next step, allowing your flows to adapt dynamically and remain reliable.

Solving orchestration challenges

Many financial systems depend on multiple services, checks, and integrations. Flowker brings orchestration to a central layer so you can manage these connections in a consistent way. You can design flexible, multi-step workflows that handle approvals, connect to providers, or branch based on transaction data. Everything is logged, versioned, and observable.

What makes Flowker different?


Purpose-built for the financial domain

Unlike generic workflow tools, Flowker is modeled specifically for the transactional ecosystem. Its architecture reflects the operational and regulatory realities of banking, payments, Pix, and financial orchestration.

Pre-ledger validation

Flowker enforces all validations before any posting reaches the ledger. This prevents inconsistent states, operational errors, and compliance violations — ensuring that only valid, authorized, and well-formed transactions are ever recorded.

Bounded contexts by design

The platform is structured around clear bounded contexts, separating concerns such as onboarding, payments, settlement, risk, and reconciliation. This segmentation improves scalability, governance, and domain clarity across complex financial operations.

Integrations with APIs, Webhooks, SDKs, and Pre-built Connectors

Flowker connects seamlessly with any external system — banking cores, fraud engines, PSPs, ERPs, or third-party APIs. As long as input/output expectations are defined, Flowker can orchestrate, transform, enrich, and route data across your ecosystem.

Full audit trails

Every step inside a workflow generates detailed audit logs that can be queried, reviewed, and exported. This provides traceability and compliance-grade visibility across the entire orchestration lifecycle.

End-to-end observability

Native support for distributed tracing, metrics, and structured logging, enabling real-time monitoring across workflows and external interactions.

Enterprise-grade security

Role-based access control (RBAC), encrypted data channels, secret management, and full compatibility with Lerian’s Access Manager.

Developer-first experience

Flowker includes CLI tools, SDKs, OpenAPI definitions, reusable templates, and a modern development workflow — enabling teams to build, test, and deploy flows with confidence and speed.

Key features


Workflow orchestration

  • Run tasks sequentially or in parallel.
  • Apply conditional logic based on HTTP status codes and response fields.
  • Persist workflow state for auditing and recovery.
  • Manage versions with full lifecycle control, including draft, promotion, rollback, and restore.

Integration and connectivity

  • Send HTTP requests (POST, GET, PUT).
  • Publish events to external queues during workflow execution.
  • Receive and process webhooks from external systems.
  • Connect to multiple financial service providers.

DSL engine

  • Define workflows with a domain-specific language (DSL).
  • Validate, lint, and simulate workflow definitions before deployment.
  • Transform data between steps and reuse templates for faster setup.
  • Import and export workflows and templates to maintain consistency across environments.

AI-assisted workflow generation

Describe a workflow in plain language and let Flowker generate a base structure for you. This feature accelerates setup and reduces human error during initial configuration.

Multi-tenancy and security

  • Complete tenant isolation through schema-based separation in PostgreSQL.
  • Support for JWT authentication (OIDC via WorkOS or Auth0) and API Keys.
  • Role-based access control (RBAC) with fine-grained policies.
  • Full audit trail with structured logs and encryption at rest.

Observability

Flowker includes built-in observability powered by OpenTelemetry, Jaeger, Prometheus, and Grafana. You can trace each workflow execution, monitor metrics, and review detailed logs for debugging and compliance.

Common use cases


Anti-fraud operations

  • Send transaction and account data to external fraud prevention services.
  • Collect and process responses from multiple providers, and apply configurable rules to decide whether to proceed.
  • Every step is logged and stored for auditing.

Manual approvals

  • Pause a workflow until a person validates the operation.
  • You can support multiple approval levels, send notifications, and integrate with approval systems.
  • Once approved or rejected, the workflow continues or stops automatically.

Payment orchestration

  • Coordinate multi-step payment flows that span multiple providers or rails.
  • Flowker handles retries, reconciliation with your ledger, and automatic recovery from failures.

Customer onboarding

  • Automate KYC and AML processes, integrate with credit bureaus and validation services, and set up conditional onboarding rules based on risk profiles.

API architecture


Flowker’s API is divided into three main categories: Authoring, Runtime, and Administrative. Each category has a clear purpose to help developers build, execute, and manage workflows.
  • Authoring routes: create, update, and manage workflow definitions, versions, and templates.
  • Runtime routes: start, monitor, and control workflow executions in real time.
  • Administrative routes: manage tenants, API keys, providers, and system health.

Current status


Flowker is in active development. For additional information about specific integrations or implementation details, contact us.