Weik.io

Introduction to Weik.io

Learn about Weik.io, the open source integration and automation platform

Weik.io is an open source integration and automation platform. It handles integrations, API management, file transfers, and event-driven architectures.

What Weik.io Does

  • Integrations - Connect systems and services using Apache Camel integration patterns
  • API Management - Create, deploy, and manage REST APIs
  • File Transfers - Schedule and monitor file transfers using Rclone
  • Event Processing - Route and process CloudEvents using NATS messaging

Platform Components

Weik.io is a distributed integration platform with six core components:

  • Backend - Central orchestration, provides REST APIs, manages configuration and state
  • Agent - Executes integrations using Apache Camel and RCLONE
  • UI - Web-based admin interface for managing integrations
  • CLI - Command-line tool for deploying and managing integrations
  • APIM - API gateway built on Microsoft YARP for API management
  • NATS - Message broker and data store for inter-component communication

Configuration

Configure Weik.io using:

  • YAML files for declarative definitions
  • REST API for programmatic control
  • CLI for command-line operations

The platform includes logging, monitoring, and OpenTelemetry support.

Deployment Options

Open Source

Self-hosted deployment with source code access. Deploy on-premises or in your own cloud infrastructure using Docker Compose.

Get Started • Docker Compose Setup

Cloud

Managed service with automatic updates and monitoring. From €49/month.

Get Started

Cloud Enterprise

Managed service with SLA and dedicated support. Deploy in your Azure account with enterprise-grade support.

Get Started

See Deployment Options for a detailed comparison.

Use Cases

  • System Integration - Connect CRM, ERP, and business systems using Apache Camel connectors
  • API Gateway - Expose and manage APIs with authentication and rate limiting
  • Data Synchronization - Transfer data between systems on schedules or triggers
  • File Automation - Move files between systems, cloud storage, and FTP servers
  • Event Processing - Route CloudEvents between services using NATS

Example Integration

A basic integration that polls a database and sends data to an API:

- from:
    uri: "timer:sync?period=300000"
    steps:
      - to:
          uri: "sql:SELECT * FROM orders WHERE status = 'pending'"
      - marshal:
          json: {}
      - to:
          uri: "https://api.example.com/orders"

This integration runs every 5 minutes (300000ms), fetches pending orders from a database, converts them to JSON, and sends them to an API endpoint.

Next Steps