- Overview
- Getting Started
- Quick Start Guide
- Core Concepts
- Users
- Models
- Creating a Model
- Model Card
- Creating a Release
- Uploading Files
- Uploading Images
- Model Templating
- Data Cards
- Creating a Data Card
- Managing Data Cards
- Using a Model
- Browsing the Marketplace
- Requesting Access
- Using a Pushed Docker Image
- Downloading Files
- Reviews
- Understanding Reviews
- Reviewing
- Reviewing a Release
- Reviewing an Access Request
- Reviewing a Model Card Lifecycle
- Review Outcomes
- Security Scanning
- File Scanning
- Image Scanning
- Inferencing
- Creating an Inference Service
- Managing Inference Services
- Model Mirroring
- Creating a Mirrored Model
- Editing a Mirrored Model Card
- Untrusted Models
- Untrusted Models
- Deletion
- Deleting a File
- Deleting a Model
- Soft Deletion
- Programmatic Access
- Authentication
- Personal Access Tokens
- Python Client
- OpenAPI Reference
- Webhooks
- Administration
- Getting Started
- Deployment Architecture
- App Configuration
- Model Lifecycle Configuration
- Schemas
- Understanding Schemas
- Create a Schema
- Upload a Schema
- Schema Migrations
- Review Roles
- Managing Review Roles
- Assigning Roles to Schemas
- Federation
- Peer Integration
- Microservices
- Artefact Scanners
- Helm
- Basic Usage
- Configuration
- Isolated Environments
- Migrations
- Bailo v0.4
- Bailo v2.0
- DataBase Scripts
- Reference
- Glossary
- Roles & Permissions
- Troubleshooting & FAQ
Federation and Peer Integration
Common questions this page answers:
- How do I connect Bailo to other instances?
- What is federation in Bailo?
- What federation states are available?
Federation connects your Bailo instance to other Bailo instances or external model repositories, allowing users to discover and mirror models from external sources.
Federation states
Your Bailo instance can operate in one of three federation states, controlled by the administrator:
- Disabled - Federation is turned off. No external sources are visible
- Read Only - Your instance can browse and mirror models from connected peers, but does not share its own models
- Enabled - Full federation: your instance both reads from and shares models with connected peers
The federation state is configured by your administrator in the application configuration.
Peer types
Bailo supports connecting to different types of external model sources.
- Bailo - Another Bailo instance
- HuggingFace Hub - The HuggingFace model repository
Additional sources can be set up by your Bailo administrator.
Configuring peers
Peers are configured in the application's backend configuration. Each peer requires:
- Base URL: The URL of the external Bailo instance or repository
- Label: A display name for the peer (shown in the Marketplace filter)
- Kind: The type of peer (Bailo or HuggingFace Hub)
- State: Whether federation with this peer is disabled, read-only, or enabled
Peer configuration is done through the app configuration file - see App Configuration.
How federation appears to users
Users see external models alongside local models in the Marketplace, with filtering by external source.
When federation is enabled and peers are configured:
- Users see a filter by external sources option in the Marketplace
- Models from external sources appear alongside local models
- Each external model shows its source
- External models can be clicked to view the source
Checking peer status
Check the reachability of connected peers through the API.
You can check the status of connected peers via the API.
Each peer has a reachability status indicating whether Bailo can communicate with it.
Related pages
- App Configuration - Where peers are configured
- Creating a Mirrored Model - Mirroring external models
- Browsing the Marketplace - Filtering by external sources
Copyright © Crown Copyright 2026.