Is Anomali cheaper than self-hosting MISP or OpenCTI?
A renewal notice or a pricing change usually triggers this question, and the honest answer is that self-hosted MISP and OpenCTI remove the license line, but not the cost. MISP is licensed under AGPL-3.0 and carries no license fee. OpenCTI Community Edition is licensed under Apache 2.0, but the Enterprise Edition features (audit logs, playbooks, organization-based segregation, SSO options and AI insights) and LTS releases require a license under the OpenCTI Enterprise Edition License. Before you compare, confirm exactly which OpenCTI features your team needs, because that decides whether the Enterprise terms are part of the cost. Ask Anomali for the price of the current subscription and each premium feed in writing, and compare it line by line with the costs below, not with the license-free headline.
The recurring costs of the open-source route sit in infrastructure and people. OpenCTI's documented sizing starts with 2 cores and at least 8 GB RAM for the platform, and 2 cores, 8 GB RAM and 16 GB SSD for Elasticsearch or OpenSearch, before you add Redis, RabbitMQ, S3-compatible storage such as MinIO, worker nodes (the documentation recommends at least one platform node for every 3 workers) and redundancy. Those nodes are paid for in your cloud or data center, and storage grows with every feed you ingest. MISP needs its own server, a database (MySQL or MariaDB, with PostgreSQL support in the 2.5 line), and Redis. Connector maintenance, feed curation, upgrades and backups are staff time, and they recur. Ask your team to estimate those hours from your current ThreatStream usage, and ask any implementation partner for a fixed-scope quote that names each component.
The one-time costs are migration, integration rework and, if needed, implementation and hardening. Migration effort depends on how many indicators, feeds and integrations you move, and on whether analysts rely on ThreatStream for threat models. Ask for a written scope that covers data export, feed re-subscription, sharing agreements, SIEM and firewall re-pointing and a parallel-run period. Also check which costs you would still pay under Anomali's own terms for air-gapped or on-premises options, because those change the comparison. The sensible decision is a cost model with three columns: current Anomali spend, open-source infrastructure and staff time, and one-time migration. If the comparison does not favor open source once staff time is included, the answer is no, and that is a valid outcome.
Which cost components move, and whether they recur
This table compares each cost component on the Anomali ThreatStream side with the same component when you run MISP or OpenCTI yourself. Read the recurring column first, because subscription and feed fees repeat each term while most self-hosted build costs are one-time, with ongoing upkeep, upgrades and staff time continuing after go-live. Use the rows to build a quote request, not as a price comparison.
| Cost component | Anomali ThreatStream | Self-hosted MISP or OpenCTI | One-time or recurring |
|---|---|---|---|
| Platform license or subscription | Subscription to the ThreatStream platform, priced under your contract terms | No license fee for MISP (AGPL-3.0) or OpenCTI Community Edition (Apache 2.0); OpenCTI Enterprise Edition needs a separate license | Recurring for ThreatStream; none for Community editions |
| Premium and commercial feeds | Vendor feeds and intelligence bundled or sold per contract | Free default feeds and open sources, plus any commercial feeds you license directly from providers | Recurring if you keep paid feeds |
| Servers and infrastructure | Largely vendor-hosted, or a vendor-supplied on-premises appliance on your side | Compute, memory and disks for MISP, or for OpenCTI's platform, workers and Elasticsearch or OpenSearch, Redis, RabbitMQ and MinIO | Recurring for hosting and hardware refresh; initial build is one-time |
| Storage and indexing growth | Storage tied to the vendor's terms, confirm retention limits in writing | Disk growth driven by indicator volume, retention policy and search index size, which you set and monitor | Recurring, growing with data volume |
| Implementation and deployment | Vendor onboarding and configuration, scope set by contract | Installation, hardening, integration with SIEM and firewalls, and configuration by your team or an implementation partner | One-time |
| Connector and integration maintenance | Vendor-maintained integrations, subject to the vendor's roadmap | Connector installs, version pinning and fixes when upstream APIs or formats change | Recurring |
| Feed curation and analyst time | Some curation handled by the vendor, depending on the package | Analysts tag, deduplicate, expire and review feeds and sharing groups in-house | Recurring |
| Migration from ThreatStream | Not applicable on the vendor side, though exit terms may apply | Export, re-mapping of indicators and sharing agreements, and parallel running before cutover | One-time |
| Support and upgrades | Vendor support included in the subscription, with level set in your contract | Community channels are free; paid support, retainers or internal staff cover upgrades, patches and incidents | Recurring |
What moves the comparison most
Six inputs shape the total cost of running MISP or OpenCTI against a ThreatStream subscription. Most of them scale with how many people, feeds, partners and retained indicators the program carries, so size these first and ask every vendor and integrator to price against the same numbers.
Analyst and user count
Every analyst who logs in consumes platform seats in ThreatStream and, in OpenCTI Enterprise, may need SSO and role separation. In MISP, users are local accounts or come through an identity provider. Count active analysts, read-only consumers and automation accounts separately, because the self-hosted cost of a small team differs little from a large one, while licensing usually does not. Ask Anomali to quote named and concurrent users in writing.
Indicator volume and retention
Indicator volume and retention period set the storage and search load on the self-hosted side. OpenCTI relies on Elasticsearch or OpenSearch, so growth in stored objects raises the size of the index cluster and its SSD. MISP stores attributes in MySQL or MariaDB, or PostgreSQL in the newer release line. Estimate events per day, average attributes per event, and how long each class of indicator must stay searchable. Confirm with Anomali which export or retention limits apply to your tier.
Sharing partners and communities
The number of organizations you exchange intelligence with changes the sharing design more than the software. MISP synchronizes events between instances and trusted communities with distribution levels and sharing groups down to the attribute level, so each partner adds a connection to configure, monitor and trust. Count partners that need bidirectional sync, one-way feeds and read-only access. Confirm how Anomali bills for shared or partner-facing access before comparing.
OpenCTI Enterprise feature needs
The Community Edition is Apache 2.0 licensed, while the Enterprise Edition adds audit logs, playbooks, organization-based segregation, full text indexing, AI insights and SSO for OpenID, LDAP, SAML, certificate and header authentication. If your controls require these features, the cost of OpenCTI shifts from infrastructure toward an Enterprise license from Filigran. Confirm which features you need, then ask both Anomali and Filigran to quote them against your user count.
Availability and recovery targets
A platform used for detection on a 24/7 basis needs redundant application nodes, database replicas, a message broker and tested backups, which roughly doubles the server footprint of a single-node lab. OpenCTI's documented sizing recommends at least one platform node for every three workers, so queue load also changes node count. Define the outage you can tolerate and the restore time you need, then price a high-availability design and a single-node design separately.
Skills already on the team
Running MISP or OpenCTI means someone patches the operating system and database, upgrades the application on its release cycle, maintains connectors and monitors queues. OpenCTI LTS releases require a specific license key and receive only critical fixes after stabilization, so on-call staff must track branch dates. A team that already runs PHP, Elasticsearch and Kubernetes carries less cost than one that does not. Count the hours your own engineers can give each month, and ask any integrator to state the support hours it covers.
How to build the comparison with your own numbers
This sequence turns a ThreatStream renewal into a three-year cost model in which every line comes from your contract, your data volume and written quotes. The result is a side-by-side view of subscription spend against the infrastructure, staff and support time that a self-hosted MISP or OpenCTI stack would need.
Collect the Anomali contract and feed list
Gather the current ThreatStream order form, the subscription term, the list of premium feeds and any add-ons such as AirGap, STAXX-related sharing or on-premises licensing. Ask your Anomali account team to confirm in writing which components are included, which are billed per year and which are usage-based. Record the renewal date and any notice period. You are done when every paid line on the invoice maps to a named component in a single spreadsheet, with no unexplained amounts left.
Inventory the indicators, feeds and integrations
Count the indicator volume you ingest and store per month, the number of distinct feeds and sharing partners, and every integration that consumes ThreatStream output, such as SIEM, firewall, EDR and SOAR connectors. Note which integrations pull through an API and which depend on exports. This inventory is the input for storage sizing and connector scope. It is complete when a colleague in the security operations team can reproduce the counts from your own logs or exports.
Size the MISP or OpenCTI stack from documented minimums
Start from the minimums in each project's documentation. For OpenCTI, the deployment overview gives platform sizing of 2 cores and at least 8 GB RAM, Elasticsearch or OpenSearch at 2 cores, 8 GB RAM and 16 GB SSD, plus Redis, RabbitMQ and S3-compatible storage such as MinIO, with at least one platform node for every 3 workers. For MISP, check the download page for the recommended Ubuntu 24.04 installer and its requirements. Scale these baselines up using your inventory, and confirm the figures with the MISP and OpenCTI maintainers or a qualified implementation partner. The output is a node-by-node bill of materials for each option.
Price server and storage lines from your own rates
Apply your cloud or data center rates to the bill of materials. Include compute, block storage, object storage for OpenCTI attachments, backup storage, network egress if you use a hosted environment, and separate environments for test and disaster recovery. Ask your cloud provider or hardware vendor for written quotes for each component. Separate one-time costs such as hardware purchase or initial build from recurring costs such as hosting, licensing for underlying operating systems and storage growth. The output is a priced annual infrastructure line for each option.
Estimate curation and connector maintenance hours
Estimate the staff time needed to maintain feeds, tune correlation or enrichment, write or update connectors for your SIEM and firewalls, and review data quality. Base the estimate on the connectors you need from the inventory and on how many feeds you curate by hand today. Note that OpenCTI ships connectors for MISP, TheHive and MITRE ATT&CK, and that MISP's feed and export tooling covers many common formats, so confirm which of your integrations already exist. Record hours per month, the role that performs each task and the loaded hourly rate your finance team uses. The output is a recurring staff cost line.
Add support, upgrade and testing time
Add the cost of vendor or partner support, if you buy it, and the internal time for upgrades, security patching and testing. For OpenCTI, factor in its release cadence: non-LTS releases ship from daily to weekly, LTS releases arrive every 6 months with one year of support each, and LTS use requires a specific license key. For MISP, factor in the move to MISP 2.5 and the project's advice that 2.4 instances are end of life. Ask any partner for a written scope and a quote covering each upgrade cycle. The output is an annual support and upgrade line that you can compare with ThreatStream's support terms.
Run the three-year model and check sensitivity
Place each line into a three-year table with one-time costs in year one and recurring costs each year. Show the ThreatStream renewal assumption next to the self-hosted totals, and state any price escalation you were quoted. Then vary the largest drivers, such as indicator volume, feed count and hourly rates, to see which assumptions move the result most. The finished model is complete when every figure cites a written quote, a documented minimum or one of your own internal records, and when a reviewer can trace each total to its source.
Where self-hosting can cost more than the subscription
Self-hosting costs more than the subscription when the people who run it are too few or too busy to keep feeds, connectors and sharing agreements current. The licence fee for MISP and OpenCTI is zero, but the staff time is not. Feed curation is the largest hidden item: someone must decide which open and commercial feeds to ingest, remove stale indicators, tune warning lists and galaxies, and check that sharing groups still match partner agreements. If that work falls to one analyst with other duties, the platform will drift even if the servers are healthy. Ask your team to estimate curation hours per week before comparing any quote with a ThreatStream renewal.
Several deployment choices move cost sharply. OpenCTI Enterprise Edition adds audit logs, playbooks, organization-based segregation, full text indexing, AI insights and SSO for OpenID, LDAP, SAML, certificate and header authentication, and it is licensed under the proprietary OpenCTI Enterprise Edition License, so you need a commercial agreement if you depend on those features. Air-gapped or sovereign deployments add the cost of moving feed updates across the gap, of offline patching and of keeping connectors current without internet access. High availability is the other driver: OpenCTI needs Elasticsearch 8.0 or OpenSearch 2.9 or later, Redis 7.1 or later, RabbitMQ 3.11 or later and S3-compatible storage such as MinIO, and each of those clustered tiers needs its own redundancy, backup and monitoring.
The MISP project is co-funded by the European Union, but that funding does not give your organization a support obligation or an SLA. Community help through the MISP support channels is valuable, but a regulated operation still needs a named internal owner or a contracted partner for incident response, upgrades and security fixes. Confirm with your procurement team whether the support you need is covered by internal staff, a retainer or a fixed-scope engagement, and write that cost into the comparison from the start.
How the cost picture differs by deployment setting
On-premises ThreatStream keeps the platform inside your data center or private cloud while feeds and platform updates still arrive through the vendor's service. You pay the subscription and premium feed fees, and you also carry the hosts, storage, backup, network paths and the people who run the deployment. Anomali's published case study describes an airline that moved to on-premises Next-Gen to meet data sovereignty requirements, which shows the driver behind this option, not a cost benchmark (Anomali airline case study).
- Infrastructure: You provide the virtual or physical hosts, storage, backup and monitoring for the appliance.
- Sync and updates: Platform and feed updates still come from the vendor, so your change windows follow their release process and your network rules.
- Staffing: Your team handles operations, integrations and upgrades, while the vendor handles product defects under the contract.
- Recurring costs: Subscription, feed fees and hardware refresh recur every cycle, and the license model determines how they scale.
Ask the vendor to list which components it supplies, which fall to you, and what outbound connectivity the on-premises deployment needs to stay current.
ThreatStream AirGap is built for disconnected sites, and Anomali publishes a datasheet describing it. The cost shifts away from network egress and toward a controlled transfer process, the isolated enclave and the people who validate and move each update across the gap. The subscription and feed terms still apply, so the comparison depends on what the datasheet and your contract include.
- Infrastructure: You run an isolated enclave with its own hardware, storage and a controlled ingest point, with no internet route.
- Update path: Feed content crosses the gap through a defined transfer process, so each update needs media handling, checksum verification and a change record.
- Staffing: A named owner must run transfers, validation and change control, and some updates may land outside business hours.
- Detection currency: A missed or delayed transfer leaves detections stale, which is an operational risk to price into the model.
Ask for the update cadence, the transfer procedure in writing, and the labor hours your team would need to move each update across the gap.
Self-managed MISP or OpenCTI, whether hosted in a cloud account, a private cloud or a data center, removes the subscription and places the full run cost on your infrastructure and staff. MISP can be installed on Ubuntu 24.04 with its installer, and it also offers Docker images, Ansible roles, Puppet modules and RPM packages (MISP download). OpenCTI depends on Elasticsearch or OpenSearch, Redis, RabbitMQ and S3-compatible storage such as MinIO.
- Infrastructure: OpenCTI's documented minimums are 2 cores and 8 GB RAM for the platform, 2 cores, 8 GB RAM and 16 GB SSD for Elasticsearch or OpenSearch, and at least one platform node for every three workers. Size MISP and OpenCTI against your indicator volume and high availability needs.
- Update path: MISP 2.5 is the recommended line, and MISP 2.4 is end of life with security fixes only. OpenCTI non-LTS releases ship from daily to weekly, while LTS releases arrive every six months, and each LTS line needs its own license key (OpenCTI product life cycle).
- Connectors and feeds: You maintain feed subscriptions and OpenCTI connectors, and curating which feeds to keep takes analyst hours.
- Staffing: Your team covers hosting, backup, upgrades, hardening and dependency patching, and the effort depends on existing skills.
Ask a partner or your own team to build a sizing and staffing model from your feed volume, retention and availability target.
Questions buyers ask before comparing cost
How much effort does running MISP or OpenCTI yourself actually take?
Effort depends on how many feeds, connectors and sharing partners you run, and on whether you use the project installers or build your own deployment. MISP 2.5 is recommended on Ubuntu 24.04 with the provided installer, and Docker images, RPM packages, an Ansible role and a Puppet module are also listed as install options. OpenCTI needs more moving parts: the platform, Python workers, RabbitMQ, Redis, Elasticsearch or OpenSearch, and S3-compatible storage such as MinIO. Ask any vendor or partner to list each component you will operate, who patches it, and how backups and restores are tested before you compare totals.
How long does a migration from ThreatStream usually take?
The duration depends on scope, and no fixed figure applies to every team. The main drivers are the volume of indicators and events to export, how many feeds and TAXII subscriptions must be re-created, how many partners share intelligence with you and must be re-onboarded, the number of SIEM, firewall and EDR integrations to re-point, and whether you need analysis objects such as actors and campaigns rebuilt in OpenCTI. Agree the scope and deliverables in writing before work starts, so the timeline follows from that scope rather than from an assumption.
What does the work need from our internal staff?
Expect to involve people from threat intelligence or SOC operations, who know which indicators drive detections, and from platform or infrastructure teams, who own servers, storage, identity and backups. Security engineers will need to validate that exported indicators still reach the right enforcement points. Someone must own feed curation after go-live, including deciding which sources to keep, tune and retire. Confirm these roles early so the work does not stall waiting for access or approvals.
Can our team run the migration without outside help?
A capable platform team can run a self-hosted MISP instance without outside help, using the project's documentation, installer and community. OpenCTI is more demanding because of its dependency stack and connector configuration, and its enterprise features such as SSO, audit logs and organization-based segregation are covered by a separate license. Outside help is usually most useful for the migration itself, for hardening and backup design, and for a documented handover. Ask any partner for a written scope that names what they will deliver and what your staff will still own.
What does an OpenCTI LTS license mean for our budget?
OpenCTI Community Edition is licensed under Apache 2.0, but LTS releases are distributed as container images that require a specific LTS license key. Under the product life cycle, LTS releases occur every 6 months and each is supported for 1 year, with a 6-month overlap between consecutive LTS versions. Check with Filigran whether the LTS key is free or paid for your use case, and whether it covers the enterprise features you need. Budget the key as a recurring line item if it applies, and compare it against the ThreatStream subscription and premium feeds you are replacing.
How do MISP and OpenCTI upgrade cadence affect ongoing effort?
Both platforms need recurring upgrade work, and the rhythm differs. MISP 2.5 is the recommended line for new deployments, and MISP 2.4 is end of life with security fixes only, so plan to stay on a supported branch and use the project's upgrade script on Ubuntu. OpenCTI uses date-based version numbers. Non-LTS releases ship from daily to weekly, so teams on those versions need a regular test and update routine. Teams on LTS releases get only critical bug and security fixes after a one-month stabilization, which lowers change volume but still requires an upgrade every 6 months or so to stay in support.
What is the recurring cost of running these platforms after go-live?
Recurring cost comes from infrastructure, staff time, connector and feed maintenance, testing of upgrades, and support. Infrastructure includes servers, storage and backup capacity, which grow with indicator volume and retention. Staff time covers patching, monitoring, curating feeds and fixing broken connectors. For OpenCTI, add any LTS license key. Ask any quote to separate one-time migration work from monthly or annual support, and to state which upgrades, backups and restore tests are included.
Why vendor ownership changes matter to the budget
Threat intelligence vendors change hands, and the budget should expect it. Mastercard completed its acquisition of Recorded Future on December 20, 2024, after announcing the deal on September 11, 2024, and Dataminr announced on October 21, 2025 that it had signed a definitive agreement to acquire ThreatConnect. Neither change says anything about how any particular product will be priced, but both show that the owner, the roadmap and the commercial terms of a platform can shift during a multi-year contract. Anomali's ownership, product packaging and renewal terms are the points to confirm in your own file rather than assume will stay fixed.
Build that uncertainty into the cost model. Ask the vendor, in writing, for the renewal uplift cap, the notice period for price changes, the list of modules and feeds that are bundled versus priced separately, and what happens to premium feed entitlements if a feed is discontinued or repackaged. Then ask for an exit clause covering the export of indicators, STIX bundles, sharing agreements and audit history, with the format and timing of that export stated in the contract. An *exit plan* is a documented estimate of what it would take to leave, written before you need it, and it becomes a line in the comparison against self-hosted MISP and OpenCTI.
Self-hosted open source changes the risk profile rather than removing it. MISP is licensed under AGPL-3.0 and OpenCTI Community Edition under Apache 2.0, so the software you run does not depend on a single vendor's renewal decision. You still depend on the upstream projects, on Filigran's Enterprise Edition licensing if you need its features, and on whoever supports your deployment. Confirm the license terms that apply to each component in your stack, and keep a current copy of your configuration and data so a change in any one supplier does not become an outage.
What to ask for in a written quote
Ask for a written fixed scope before any cost comparison is finalized, because the self-hosted figures only mean something once the components are named. The quote should list the servers and storage for each platform separately. For OpenCTI, that means the platform nodes, the Python workers (the documented guidance is at least one platform node for every 3 workers), Elasticsearch or OpenSearch, Redis, RabbitMQ and S3-compatible storage such as MinIO. For MISP, it means the application host, the database (MySQL or MariaDB, or PostgreSQL on MISP 2.5 where your team has confirmed it fits your standards), Redis and the backup target. Ask for each sizing assumption in writing, and confirm current minimums against the OpenCTI deployment overview and the MISP download page rather than relying on figures in a proposal.
Next, require an explicit connector list and curation estimate. Name every feed, MISP or OpenCTI connector, enrichment source and SIEM or firewall integration in scope, and state whether each one is built, configured, or only documented for your team to run. Ask how many analyst hours per week are assumed for feed triage, false-positive review and sharing decisions, and who owns that time after handover. On upgrades, request the handling for MISP release cadence and, for OpenCTI, the choice between regular releases and the LTS line. Confirm who holds the LTS license key, since LTS images require one, and whether the quote covers patching during the post-stabilization period when only critical and security fixes ship.
Finally, pin down support hours, response expectations, migration boundaries and exit terms. Ask which period is fixed-scope implementation and which period is an optional retainer, and what each includes. Require the migration boundary in writing: which ThreatStream exports, which indicators and feeds, which sharing partners and which integrations move, and which are the customer's responsibility. Ask for the handover documents, the admin credentials and infrastructure as code the customer keeps, and the conditions for ending a retainer. DeployOpen does not publish a price list, and a quote follows from the written scope, so the more precisely these items are defined, the more comparable the offers you receive will be.
How DeployOpen scopes a fixed-price implementation
DeployOpen plans and implements self-hosted MISP or OpenCTI inside your own infrastructure, from cloud accounts to air-gapped networks. Engagements are fixed-scope, so the cost components of your ThreatStream replacement are agreed in writing before any work starts.
How we scope
- Written scope lists which ThreatStream feeds, indicators, sharing groups and integrations move to MISP or OpenCTI
- We size servers and storage for the platform, search, Redis, RabbitMQ and object storage components you choose
- Scope names connector maintenance, feed curation and staff training as separate line items for your quote
How we build
- We install MISP 2.5 or OpenCTI in your environment with the deployment method your team already operates
- Connectors for SIEM, firewall and enrichment tools are configured and tested against your live data flows
- Sharing groups and synchronization with trusted partners are set up and verified against agreed test cases
How we hand over
- Documentation covers configuration, upgrade steps, backup procedures and the connector inventory for your team
- Testing results, access control settings and data flow diagrams are delivered as written evidence
- Knowledge transfer sessions prepare your operators to run feed updates and routine maintenance without us
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Retainers can cover OpenCTI LTS license handling and MISP version upgrades on a schedule you agree
- Ask us to confirm which support tier and response terms apply before you sign the written scope

