Book a demo
Workflow Studio · integration and backend

Connect your systems. Ship the APIs your apps call.

Draw integrations and backend logic on a canvas. Alphanetix compiles them into Java services and runs them on your own machines.

Book a demoRead the docs
Workflow Studioinvoice-sync v2.3Live
⏱
Every 15 minutesschedule
ERP
Fetch invoicesyour ERP · REST
⇄
Map the fieldsattribute mapping
DB
Match the ledgerPostgreSQL · transaction
CRM
Post to the CRMyour CRM · REST
#
Write the recordaudit log
From canvas to service

Five steps, one screen.

Click through how a workflow goes from a drawing to a service running on your servers.

Draw the process.

Start from an HTTP endpoint or a schedule, pick connectors from the library, and arrange the steps on a canvas.

  • Every workflow is three layers: data sources, attribute mappings and logic.
Workflow Studioinvoice-sync v2.3Live
⏱
Every 15 minutesschedule
ERP
Fetch invoicesyour ERP · REST
⇄
Map the fieldsattribute mapping
DB
Match the ledgerPostgreSQL · transaction
CRM
Post to the CRMyour CRM · REST
#
Write the recordaudit log

Drag a field to the field it becomes.

The mapping designer draws one line per field, readable at a glance by the people who own the data.

Workflow StudioMapping designer
customer.idparty_id
amount.valueamount_minor
invoice.dateposting_date
currencyiso_currency

Business rules without hand-written code.

The Logic Builder covers decisions, calculations and loops nested to any depth, with an AXL text view for those who prefer it.

  • 150+ operations in 13 categories.
  • Your own Java, imported as team-scoped, versioned functions.
Workflow StudioLogic BuilderAXL view
IfLoopAddMultiplyRoundSubstringDate addLookup150+ operations
instalment = round(total * rate / (1 - (1 + rate) ^ -months), 2)

Compiled, not interpreted.

A deterministic generator writes Java on Eclipse Vert.x. Same workflow, same code. No language model writes production code.

  • About 7,600 requests per second per CPU core, measured as 122,000 on one 16-core Intel i9-12900K.
Workflow StudioClaimsService.javageneratedclaims-service-2.3.jar
public final class ClaimsService extends AbstractVerticle { public void start() { router.get("/claims/:id/status").handler(this::status); router.post("/eligibility/check").handler(this::eligibility); timers.daily("02:00", this::reconcile); } }

Shipped to machines you register.

Deploying sends the JAR over SFTP, starts it over SSH and health-checks it until it is live. Memory, threads and ports are set per service.

  • Clusters with Hazelcast locally or Infinispan globally, applied as a staged topology.
  • Per-environment IP allow and deny lists.
Workflow StudioEnvironmentsProduction3 machines
app-01 · 10.0.2.11claims-serviceeligibility
app-02 · 10.0.2.12loan-application v1.4
app-03 · 10.0.2.13reconciliation
Backend for your apps

Your workflows are your APIs.

Start a workflow with an HTTP endpoint and it becomes an API your web and mobile apps call.

  • Documented for you: a read-only, revocable portal with OpenAPI 3 export. It never exposes how the flow works inside.
  • Versioned like code, with every publish recorded.
Workflow StudioAPI documentationlendingRevoke linkExport OpenAPI 3
POST/quotesPOST/applicationsGET/applications/:idGET/rates
POST/quotesv1.4 · live
amountnumber
monthsinteger · 12 to 84
customer_idstring
200 { "monthly": 368.40, "term": 36 }
AI for your own team

Describe it. AI drafts it. A person publishes it.

Write the process in plain words. AI drafts the workflow using only the connectors your team really has.

  • A draft, not production code. The same deterministic generator compiles it once a person publishes.
Workflow StudioAI flow generationDraft
Describe the processEvery night, match settled payments to the ledger and flag mismatches.
⏱
Every night at 01:00schedule
{}
Fetch settled paymentsyour payment provider
DB
Match the ledgeryour PostgreSQL
R
Flag mismatcheslogic
✓ Built from connectors your team already hasReview and publish
Around the workflow

Everything it takes to run in production.

Publishing is a commit.

Every publish gets a major.minor version and a message in git, so changes roll forward with a record.

v2.3 · add fee reversal
v2.2 · new pricing table
v2.1 · initial release

Watch it run.

Service health and activity for every microservice, visible in Studio.

claims-servicehealthy
eligibilityhealthy

Bring the assistant you use.

The MCP server lets Claude, Cursor or Copilot list, create, validate and deploy workflows, through the same APIs and checks as a person.

› validate fee-reversal
✓ valid · connectors resolved

Workflows reach your systems.

REST and HTTP APIs, and SQL databases with transactions across steps.

PostgreSQLOracleSQL ServerMySQLMariaDBDB2REST · HTTP

More than 1,800 systems.

One connector library, shared with Agent Studio on the Suite.

The connector library →
Talk to our team

Bring a process you run by hand.

We will draw it with you, compile it, and show it running on a machine like yours.

Book a demoAdd agents with the Suite