Welcome to the OpenAEV Docker deployment guide! This guide provides resources and information to help you deploy and manage OpenAEV using Docker.
For detailed instructions on installing OpenAEV using Docker, refer to the OpenAEV documentation space.
OpenAEV is actively under development. If you encounter bugs, have feature requests, or need help, please report them using the GitHub Issues module. We appreciate your feedback and contributions to improve the platform.
Join our community to engage in discussions, share ideas, and get support:
- Slack Channel: Connect with us on Slack
The OpenAEV stack is modular and uses multiple Docker Compose files for easier configuration:
Important
Remember to create a .env file from .env.sample and customize the configuration as needed.
To start OpenAEV with the essential services, run:
docker compose -p openaev -f docker-compose.yml up -dTo start OpenAEV with the Caldera executor (Caldera used as an agent), run:
docker compose -p openaev -f docker-compose.yml -f docker-compose.caldera.yml -f docker-compose.caldera-executor.yml up -dTo start OpenAEV with the Caldera injector (Caldera used as an implant), run:
docker compose -p openaev -f docker-compose.yml -f docker-compose.caldera.yml -f docker-compose.caldera-injector.yml up -dOpenAEV allows you to customize your stack by selecting specific collectors and injectors to meet your unique needs:
- Additional Collectors: Explore a variety of collectors available here.
- Additional Injectors: Discover injectors to enhance your simulations here.
This stack bundles XTM One, Filigran's AI-powered assistant, alongside OpenAEV. The following services are started by default:
| Service | Description |
|---|---|
xtm-one |
XTM One platform (web UI + API, exposed on XTM_ONE_PORT) |
xtm-one-worker |
XTM One background worker |
pgsql-xtm-one |
Dedicated PostgreSQL + pgvector instance for XTM One |
XTM One reuses the shared redis and minio services and connects to OpenAEV internally via OPENAEV_API_URL. OpenAEV registers itself with XTM One using PLATFORM_REGISTRATION_TOKEN — this shared secret must be identical across every platform connected to the same XTM One instance.
All XTM One configuration (admin credentials, dedicated Postgres credentials, S3 bucket, license, log settings) lives in the XTM ONE section of .env.sample. Once the stack is healthy, XTM One is available on http://localhost:${XTM_ONE_PORT} (default 8090).
OpenAEV is a product designed and developed by the company Filigran.
