Deploy OpenCTI
OpenCTI threat intelligence platform: full stack with 10 connectors
Just deployed
Connector MITRE ATT&CK
Just deployed
Connector Import YARA
Just deployed
Connector Document Analysis
Just deployed
RabbitMQ
Just deployed
/var/lib/rabbitmq
Connector Export STIX
Just deployed
Elasticsearch
Just deployed
/usr/share/elasticsearch/data
Connector Import STIX
Just deployed
Just deployed
/data
Connector OpenCTI Datasets
Just deployed
Connector Import Document
Just deployed
Connector Export CSV
Just deployed
Connector External Reference
Just deployed
Just deployed
Redis
Just deployed
/data
Connector Export TXT
Just deployed
Deploy and Host OpenCTI on Railway
OpenCTI is an open-source (Apache-2.0) cyber threat intelligence platform by Filigran. It stores threat actors, malware, attack patterns, indicators, reports and their relationships as a STIX 2.1 knowledge graph, and imports, enriches and shares that data through connectors, a GraphQL API and a web UI with dashboards and investigations.
About Hosting OpenCTI
OpenCTI needs several cooperating services: the platform (UI and API), Elasticsearch for the knowledge graph, Redis for caching and event streams, RabbitMQ for work queues, S3-compatible storage for files, and workers that write ingested data. This template runs OpenCTI 7.261119.0 with that full stack as 16 Railway services wired over the private network. Every stateful service keeps its data on its own volume, all passwords and tokens are generated at deploy, and the platform and connectors wait for their dependencies, so the stack comes up in the right order. The first start takes about 5 to 10 minutes while the platform creates its indexes.
Common Use Cases
- Build a shared knowledge base of threat actors, campaigns, malware and indicators for a security team
- Import MITRE ATT&CK, STIX bundles, PDF reports and YARA rules, then link and enrich them
- Export curated intelligence as STIX, CSV or plain text for SIEMs, firewalls and partners
Dependencies for OpenCTI Hosting
- Elasticsearch 8, Redis, RabbitMQ and S3-compatible object storage (all included)
- About 8 GB of RAM across the stack; Elasticsearch and the platform use most of it
Deployment Dependencies
- OpenCTI source: https://github.com/OpenCTI-Platform/opencti
- OpenCTI documentation: https://docs.opencti.io
- Template repo: https://github.com/aalfath/opencti-railway-template
Implementation Details
Services in this template:
- OpenCTI (public): the platform, web UI and GraphQL API on port 8080. Railway's health check uses
/healthonPORT8081, a small relay that calls OpenCTI's health endpoint with the generatedAPP__HEALTH_ACCESS_KEY, so the key stays secret. - Worker: writes the data that connectors queue in RabbitMQ into the platform.
- Elasticsearch (volume): the knowledge graph store, single node, password protected.
- Redis (volume): cache, locks and the live event stream.
- RabbitMQ (volume): queues between the platform, the worker and the connectors.
- Silo (volume): S3-compatible storage for uploaded and exported files (the MinIO fork OpenCTI's own docker-compose uses).
- 10 connectors, the set from OpenCTI's docker-compose: Export STIX, Export CSV, Export TXT, Import STIX, Import Document, Document Analysis, Import YARA, External Reference, OpenCTI Datasets (sectors, countries, regions) and MITRE ATT&CK.
After deploy:
- Wait until the OpenCTI service is healthy, then open its public URL.
- Sign in as
admin@opencti.iowith the password in the OpenCTI service'sAPP__ADMIN__PASSWORDvariable (generated at deploy). Change the email and password under your profile. - The OpenCTI Datasets and MITRE ATT&CK connectors load their data in the background during the first hour.
To add another connector from the OpenCTI catalog, add a service from its official image with OPENCTI_URL and OPENCTI_TOKEN set as on the existing connectors, plus its own CONNECTOR_ID (a new UUID). To scale ingestion, raise the Worker service's replicas. Optional features such as SMTP or SSO are set with OpenCTI's own variables on the OpenCTI service (see the OpenCTI documentation).
Updates: this template builds from the GitHub repo above, so when the pinned version is bumped, Railway shows an "update available" notice on your project and you choose when to apply it. Read CHANGELOG.md in the repo first.
Why Deploy OpenCTI on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying OpenCTI on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Connector MITRE ATT&CK
aalfath/opencti-railway-templateConnector Import YARA
aalfath/opencti-railway-templateConnector Document Analysis
aalfath/opencti-railway-templateRabbitMQ
aalfath/opencti-railway-templateConnector Export STIX
aalfath/opencti-railway-templateElasticsearch
aalfath/opencti-railway-templateConnector Import STIX
aalfath/opencti-railway-templateConnector OpenCTI Datasets
aalfath/opencti-railway-templateConnector Import Document
aalfath/opencti-railway-templateConnector Export CSV
aalfath/opencti-railway-templateConnector External Reference
aalfath/opencti-railway-templateRedis
redis:8.2Connector Export TXT
aalfath/opencti-railway-template