Platform Overview

Bifrost Integrations is an open-source automation platform designed to democratize best-in-class tooling for the emerging Integration Services industry - before venture capital gets the chance to own something we’re all incredibly passionate about: solving problems with automation.

What Bifrost Solves

Existing RPA platforms are great for rapid development and provide helpful abstractions for things like OAuth, but they cannot and will not keep pace with AI-powered development and have always been constrained by limitations that traditional programming languages do not have.

Bifrost Integrations removes those limitations by creating a light management layer with the features that make RPA’s uniquely valuable and letting Python do what it’s good at. It’s architected with multi-tenancy at its core, enabling you to scale your Integration Services business without duplicating work across customers. This is not another RPA tool trying to be everything to everyone; it’s a platform designed specifically to help you build scalable automation businesses the right way, without vendor lock-in, and without the limitations of RPA.

Tip

Want to understand the “why” behind Bifrost? Check out Why This Matters to learn about our mission.

What You Can Do with Bifrost

Develop with Your Favorite Tools

• Use VS Code, Claude Code, and Git for version control
• Build with Python and modern development workflows
• Test locally before deploying to production

Build Reusable Integrations

• Create integration modules for common platforms (NinjaOne, HaloPSA, Pax8, Microsoft CSP)
• Abstract authentication, pagination, and API complexity
• Share functionality across all your workflows

Centralized Connection Management

• Automated OAuth refresh flows
• Key/value configuration storage per organization
• Secure secrets management with Azure Key Vault

Dynamic Forms and Workflows

• Create flexible forms for you and your customers
• Build context-aware workflows that adapt based on organization and user
• Generate form inputs programmatically from data providers

Multi-Tenant Architecture

• Scope functionality globally or to specific organizations
• Deliver value to customers without code duplication or redeployment
• Complete data isolation between tenants

AI-Assisted Development

• Built for modern AI coding workflows
• Use Claude Code, GitHub Copilot, and other AI tools
• Write workflows from natural language descriptions

Core Architecture

┌─────────────────────────────────────────┐
│  Client (React SPA)                      │
│  Forms | Workflows | Admin               │
└────────────────┬────────────────────────┘
                 │ REST API
                 ▼
┌─────────────────────────────────────────┐
│  Azure Functions Runtime                 │
│  ┌───────────────────────────────────┐  │
│  │ HTTP Handlers                     │  │
│  │ Workflow Registry                 │  │
│  │ Execution Context                 │  │
│  └───────────────────────────────────┘  │
└────────────────┬────────────────────────┘
                 │
                 ▼
┌─────────────────────────────────────────┐
│  Azure Storage | Key Vault | Services   │
└─────────────────────────────────────────┘

Core Concepts

Workflows

Python async functions decorated with @workflow:

@workflow(name="create_user", description="Create new user")
@param("email", "email", required=True)
async def create_user(context, email: str):
    return {"user_id": "123"}

These are used to simply tell the platform what code is available to be tied to things like forms, and register things like scheduled jobs and webhooks.

Forms

UI for workflows with:

• Multiple field types
• Data provider integration for dynamic lists
• Visibility rules
• Real-time validation

Data Providers

Dynamic options for dropdowns:

@data_provider(name="get_departments")
async def get_departments(context):
    return [
        {"label": "Engineering", "value": "eng"},
        {"label": "Sales", "value": "sales"}
    ]

Discovery System

Workflows auto-register on startup and during execution:

1. Scans your workspace directory
2. Imports Python files with the proper decorators
3. Registers metadata
4. Exposes via REST API

This can be an intense process, but it’s important to allow your code base to be organic and organized how you want, rather than struggling with organizing it within a web interface. This enables you organize things by feature, customer or whatever you find the most useful.

Multi-Tenancy

• Organization Isolation: Context provides information about who the caller is so you can make decisions in your code
• Org-Scoped Secrets: Stored as configurations, configs and secrets will default to the caller’s organization first and call back to global secrets with the same name.
• Forms: Forms are essentiall how you expose workflows in a user-friendly way and can be scoped to an organization. Today, form configuration exists in the database and is designed in the UI.

Security

• Authentication: Entra ID (untested, but you should be able to configure any oauth provider)
• Authorization: Role-based access control (RBAC) to forms
• Secret Management: Azure Key Vault
• Audit Logging: Most actions logged with user context
• OAuth Flow: Secure OAuth 2.0 token management, also stored in Key Vault

Use Cases

MSP/IT Service Providers

• User onboarding/offboarding
• License management
• Ticket automation
• Service request forms
• Compliance reporting

Enterprise IT

• Multi-system user provisioning
• Self-service capabilities
• Bulk operations via forms
• Line-of-business app integration

Integration Services

• Data synchronization
• Event-driven workflows
• API orchestration
• Custom business logic

Open Source

• License: AGPL
• API Repo: github.com/jackmusick/bifrost-api
• Client Repo: github.com/jackmusick/bifrost-client

Next Steps

• Installation Guide - Deploy to Azure
• First Workflow Tutorial - Build your first workflow
• Create Forms - Build dynamic forms
• OAuth Integration - Connect external APIs