One platform to design, build and ship every integration.

Projects, microservices and flows.

Group related integrations into projects. Each microservice deploys and scales independently. That's API-led architecture without the runtime overhead.

• Project

  A home for related integrations, shared by your team.

• Microservice

  Each one compiles to its own Go application.

• Flows, APIs, configurations and types

  The building blocks inside every microservice.

Project
 └── Microservice (each one compiles to its own Go application)
      ├── Flows & Error-Handler Flows
      ├── API Paths (RAML / OpenAPI driven)
      ├── Global Configurations (reusable connections)
      └── Type Definitions (schemas)

Real code you own, ready to run.

Every microservice ships with:

• Clean Go source code (main.go, handlers and configuration)
• Built-in listeners for the triggers you designed (HTTP, messaging, file, scheduler and more)
• Structured logging configuration
• A /health endpoint for load balancers and orchestrators
• A multi-stage Dockerfile
• Environment-based configuration (.env.example)
• A README with build-and-run instructions

order-api/
├── main.go
├── handlers/
│   ├── get_orders.go
│   └── create_order.go
├── config/
│   └── config.go
├── logging.yaml
├── Dockerfile          # multi-stage build
├── .env.example        # environment-based config
├── go.mod
└── README.md           # build-and-run instructions

$ ./order-api
listening on :8081 · GET /health → 200 OK

Illustrative example. Generated output varies by project.