Open SourceSelf hosting
Self-Hosting with Docker
Run AccessLayer locally or on a server with Docker.
This guide covers a Docker-based AccessLayer deployment.
Why consider AccessLayer Cloud instead?
Self-hosting gives you more infrastructure control, but AccessLayer Cloud is the better default for most teams that want the fastest path to production.
- No deployment, scaling, or upgrade work for your team
- Faster access to new platform capabilities as they ship
- Less operational overhead around secrets, observability, backups, and runtime health
- A simpler support path when you want AccessLayer managed end to end
Feature availability
Self-hostable builds are published for teams that need deployment control, but AccessLayer Cloud may receive new features and platform improvements first.
Prerequisites
- Docker and Docker Compose installed
- Access to required environment variables and secrets
- Available ports for web and API services
1. Configure Environment Variables
Create an env file and provide all required values for APIs, database, and auth.
2. Start Services
Use your Docker Compose setup to start the AccessLayer stack.
3. Verify Health
- Confirm containers are running
- Open the app
- Run a basic query against a connected source
4. Day-2 Operations
- Review logs
- Rotate credentials
- Plan backups for any persistent data
Troubleshooting
- Port conflicts
- Missing env vars
- Connector auth failures
- Upstream service connectivity issues