Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.timbal.ai/llms.txt

Use this file to discover all available pages before exploring further.

Deploy your Timbal applications on your own infrastructure using Docker containers. This approach gives you full control over your deployment environment while leveraging the same containerized approach used by the Timbal Platform.

​
Prerequisites

Before self-hosting your Timbal application, ensure you have:
  • Timbal CLI installed and configured
  • A Timbal project initialized with timbal init
  • Your application tested locally
  • Docker installed on your target infrastructure

​
Deployment Process

The first two steps are identical to the Timbal Platform deployment:
1

Prepare your environment

Configure your .dockerignore and timbal.yaml files.
2

Build your application

Create your Docker container with timbal build.
3

Launch your container

Run your containerized Timbal application using Docker:
docker run -d -p <port>:<port> <image_tag> \
  uv run -m timbal.server.http --port <port> --import_spec <fqn>
This command starts the Timbal HTTP server directly with your specified agent or workflow. The --import_spec parameter should match the fqn from your timbal.yaml configuration file, defining which component to execute.
You can add as many environment variables as needed with the -e docker flag.
A timbal serve command will be available soon to simplify this process.

​
Accessing Your Application

Once running, your Timbal application exposes a REST API accessible at: 
POST http://localhost:<port>/collect
For streaming responses: 
POST http://localhost:<port>/stream
For complete API documentation, including request/response formats, visit the API Reference.

​
Production Considerations

​
Container Orchestration

For production deployments, consider using:
  • Docker Compose for multi-container applications
  • Kubernetes for scalable, managed deployments
  • Docker Swarm for simpler orchestration needs

​
Monitoring and Logging

  • Configure log aggregation to collect container logs
  • Set up health checks for container monitoring
  • Implement metrics collection for performance monitoring
Even with self-hosted deployments, you can still use Timbal Platform for tracing, monitoring, and observability by configuring your application to connect to the platform services.

​
Security

  • Run containers with non-root users when possible
  • Use secrets management systems instead of environment variables for sensitive data
  • Keep base images updated for security patches