What's Bloomberry?
Bloomberry is an API product from Revealera, which has been selling hiring and technology adoption data to hedge funds since 2020, including 3 of the 20 largest funds in the world.
We cover 1,700+ B2B products across 190 categories - from HR tech and security tools to devops, AI platforms and vertical software. Full category list: https://app.bloomberry.com/categories.txt
Example signals: "ZoomInfo just subscribed to Zoom" (adoption), "Stripe just unsubscribed from Salesforce" (churn), or "Logitech started tracking cold email campaigns with Apollo.io" (usage).
Who is this data for?
Bloomberry is built for sales platforms, enrichment layers, intent products and AI SDR tools that want to ship distinctive signals to their own users - as well as GTM teams building internally.
If you're a platform, this is data your customers see. Common integrations:
Signal feeds. Surface "recently churned from a competitor" or "renewal approaching" directly in your product, as a signal type your users can filter and act on.
Enrichment and account scoring. Attach recent technology adoption, competitive churn events and current vendor usage to accounts your users already have, so they can prioritise outreach.
List building and audience targeting. Let users build segments on technology behaviour, like companies that adopted a DevOps tool in the last 90 days.
You don't need to build or maintain any collection infrastructure. It's a REST API with JSON responses.
How do I get an API key?
Sign up for a free API key with 1,000 credits to test the API at https://bloomberry.com/signup.html
If you're evaluating Bloomberry for a product integration and need a larger trial, email us at [email protected] with your use case and we'll set one up. We're a small team and we answer directly.
What type of companies do you cover?
Our dataset spans Fortune 500 enterprises down to small businesses with 5+ employees, across all major global markets. SMB coverage matters for many use cases - enterprise adoption signals are valuable, but technology decisions at smaller organisations are often more actionable.
Our geographic reach extends beyond the US to every major global market, with specialised coverage of region-specific software where relevant.
Where does the data come from?
Bloomberry reads infrastructure signals. In comparison, BuiltWith and Wappalyzer read websites; TheirStack reads job postings. We however, watch what a company sets up when it buys software.
Concretely, that means new subdomains, DNS records, certificate transparency logs, and signals specific to how each individual product gets deployed. We crawl websites too, but we go further than checking whether a tag exists - we read the configuration inside script files and check whether they still return a working response.
We've built a separate detector for each of the 1,700+ products we cover, so we know what that particular product looks like when it's set up, and we can confirm when it's gone. That's why we can tell you when a company subscribed or churned, not just what's on their website today.
Some of those signals only appear when a product is genuinely deployed. Rolling out an AI assistant or an ERP across an organisation usually means verifying a domain for single sign-on or updating email records - public changes that a single seat or a free trial never produces. So when we report an adoption, it generally reflects a real organisational rollout rather than one user signing up.
We do not use job postings, vendor case studies or product reviews. Those sources are indirect and they lag.
What are the weaknesses of your data?
We'd rather you know these up front than discover them in evaluation.
Company level, not person level. We identify when an organisation makes a technology decision, but not the individual responsible for it. We don't provide contact data.
Category gaps. We're strong across most B2B categories, but thinner in some niches - edtech is the clearest example.
How real-time is your data?
Purchase and usage signals typically appear within 3-7 days of the actual technology adoption.
Churn detection involves additional validation to ensure accuracy, so churn signals may have longer latency - typically 1 to 2 weeks. We consider this a worthwhile trade: a false churn signal sent to your users is worse than a slightly slower true one.
How is this different from BuiltWith, Wappalyzer or TheirStack?
BuiltWith and Wappalyzer detect what's present on a company's website. That works for front-end technologies, but it tells you presence rather than timing, and it misses backend and enterprise software entirely - security infrastructure, HR systems, ERPs, internal CRMs and financial software leave no website footprint.
TheirStack infers technology usage from mentions in job postings and scores how likely it is that a company actually uses what it mentioned.
Two consequences worth knowing if you're evaluating us technically:
We don't call it churn just because a tag disappeared. A vanished script usually means a site redesign, not a cancellation. We verify the endpoint is genuinely dead before reporting churn.
We add new products continuously. Because each product gets its own detector, we can cover tools shortly after launch - including recent GTM, AI and infrastructure products that crawl-everything indexes and job-posting datasets tend to miss. We track deployments of things like n8n, LiteLLM, Resend and MCP servers, none of which reliably appear on a website or in a job ad.
If you need a product we don't cover yet, tell us and we'll try to add it.
