CRM
cobra CRM
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by cobra computer's brainware GmbH · www.cobra.de
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
cobra CRM, from Konstanz-based cobra computer's brainware GmbH, scores highest on automation and integrations, both spanning 4 to 5: the pages publish multi-step claims — event flows from invitation through certificates and follow-up, real-time workflow monitoring that distributes tasks automatically, and a directory naming ERP, DMS, Office 365 and DATEV among over 100 further systems. Sovereignty scores span 4 to 6, crediting a German entity, an on-premise option in the customer's own data center and Art. 28 GDPR contracts with EU-based website hosts; judges flag that the German cloud location appears only in homepage marketing, the privacy policy does not state where cobra CRM Cloud customer data is hosted, and the page says a US transfer cannot be excluded for Google and Microsoft. Data portability is the floor, spanning 1 to 2, with no public information on import, export or migration. Contact management and sales pipeline spread 2 to 4 over how far promised forecasts deserve credit without public information on stage requirements, win/loss capture or quota tracking. Pricing appears only as a free cloud trial; no figures are published.
Speaks for it
- Automation scores span 4 to 5 on published multi-step claims, including workflows monitored in real time with automatic task distribution.
- Integrations score 4 to 5, naming ERP, DMS, Office 365 and DATEV among over 100 further systems.
- Sovereignty scores span 4 to 6, crediting a German entity, an external data protection officer and an on-premise option in the customer's own data center.
- Art. 28 GDPR contracts are in place with the named EU-based website hosting providers.
- A free trial registration for cobra CRM Cloud is published on the vendor's site.
Held against it
- Data portability scores span 1 to 2, with no public information on import, export or migration tooling.
- No public information exists on sales pipeline stage requirements, win/loss capture, quota tracking or a custom report builder.
- The privacy policy does not state where cobra CRM Cloud customer data is hosted, and no subprocessors are disclosed for the CRM Cloud product itself.
- No public information exists on API documentation, webhooks, two-way email and calendar sync or rate limits.
- No price figures, tiers or per-seat rates appear on captured pages, and add-on modules are named without prices.
Best for
- You want routine sales and marketing automation — address capture, history entries, automated serial emails — monitored in real time.
- Your stack is German-market and needs ERP, DATEV and Office 365 among the over 100 named connections.
- You want an on-premise deployment in your own data center from a German vendor.
- You organize events and want invitation, participant management, certificates and follow-up handled inside the CRM.
Avoid if
- You must plan your exit before signing — we found no public information on import, export or data-return terms.
- Your finance team needs an enforced forecast process with stage requirements, win/loss capture and quota tracking.
- You need documented API endpoints, webhooks or two-way email and calendar sync, not just a named integration directory.
- You need published per-seat prices and tier structures to budget before a sales conversation.
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
The captured pages show structured contact records with classification, potential, industry and territory filtering plus automated history entries and address capture — more than a flat address book, but I see no relation model underneath. We found no public information on custom fields, deduplication or merge tooling, or on how people, companies and deals connect, so I can't tell how far the data model bends. 4 5
The Data Protection Officer
The captured pages evidence documented customer contacts with history entries, quote creation and leads filterable by classification, industry, potential and territory. We found no public information on custom field types, deduplication or merge tooling, required fields or field-level permissions, so record hygiene beyond classifications stays unevidenced. 4 5
The Sales Ops Lead
Address records carry classification, potential, industry and territory fields with automated history entries, which is real segmentation for territory planning. We found no public information on required fields, duplicate detection or merge tooling — the hygiene controls that keep a shared database clean at 40 seats. 4 5
The RevOps Integrator
Contact documentation, history entries and segmentation of leads by classification, potential, industry and territory are evidenced, but that is segmentation rather than a data model. We found no public information on custom field types, required fields, deduplication or merge tooling, so the depth a complex account structure needs is unevidenced. 4 5
The Migrator
Customer contacts with classifications, industries and territories, history entries on the record, and offer creation with order and revenue analyses are the depth the pages actually show. I found no public information on custom field types, required fields, merge or deduplication tooling — and dedupe is the first thing I look for before importing thousands of messy rows, so that silence decides it. 4 5
The Skeptic
Automatic history entries and contact documentation are evidenced, and leads can be filtered by classification, potential, industry and territory — that is the whole of the published record model. We found no public information on custom field types, required fields, duplicate detection or merge tooling, so nothing shows duplicates being caught rather than accumulating. 4 5
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Forecasts, performance tracking and order and revenue analyses are named, and pipeline tasks like follow-up, reminders and regular contact are automated — forecast views exist in the marketing copy at least. We found no public information on stage requirements, win/loss capture or a custom report builder, so this sits between canned reporting and a real process. 4
The Data Protection Officer
The pipeline page claims forecasts, performance tracking and order and revenue analyses, alongside automated follow-up tasks and reminders for the sales team. We found no public information on stage requirements, multiple pipelines, forecast composition by team or period, or quota tracking, so no enforced process is evidenced. 4
The Sales Ops Lead
The pages promise forecasts and performance tracking with order and revenue analyses and automated follow-up tasks, but we found no public information on stage requirements, win/loss capture, quota tracking, forecast views by team and period, or a custom report builder. None of the enforcement a CFO-grade forecast rests on is evidenced. 4 5
The RevOps Integrator
Forecasting and performance tracking appear as a single marketing line, alongside offer creation, order and revenue analyses, and automated pipeline tasks like follow-up reminders. Nothing public shows stage requirements, win/loss capture, quota tracking or a custom report builder, so I cannot treat the forecast as something a finance team would sign. 4
The Migrator
A dedicated pipeline page promises forecasts and performance tracking, automated follow-up tasks, reminders and scheduled contact, plus revenue analyses. I found no public information on stage requirements, required fields per stage, win/loss capture, quota tracking or a custom report builder, so I cannot credit a process that is enforced rather than suggested. 4
The Skeptic
Forecasts, performance tracking and order and revenue analyses are each promised in a single line, alongside automated follow-up, reminders and tasks for the sales team. We found no public information on stage requirements, win and loss capture, quota tracking or a custom report builder, so a finance department is asked to take the word "Prognosen" purely on faith. 4
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
Routine task automation — address capture, history entries, print jobs, automated email dispatch — plus workflows the system monitors in real time, distributing tasks automatically, reads like multi-step automation with basic routing. We found no public information on delays, branching, webhooks as steps or sequence analytics, so I stop short of calling it a full builder. 5 6
The Data Protection Officer
Multi-step automation is claimed: routine tasks such as address capture, history entries and automated email dispatch, real-time workflow monitoring that distributes tasks automatically, and automated lead capture and nurturing flows. We found no public information on a workflow builder with branching and delays, sequence analytics, error handling or usage caps. 5 6
The Sales Ops Lead
The product claims workflow monitoring with real-time change detection, automatic task distribution, automated serial emails and lead-nurture automation — more than simple record triggers. We found no public information on branching, delays, sequence analytics or workflow limits, so the builder's depth stays unverifiable. 5 6
The RevOps Integrator
Automated routine tasks, real-time workflow monitoring that distributes tasks automatically, and lead-nurture campaign automation are all claimed. But we found no public information on a workflow builder with branching and delays — and, my sticking point, none on webhooks as steps, error handling or sequence analytics. 5 6
The Migrator
Automated routine work — address capture, history entries, print jobs, automated email sending — plus a system that monitors individual workflows, detects changes in real time, distributes tasks automatically and informs customers or the team, and marketing automation for lead capture, data maintenance and communication. I found no public information on delays, branching, webhook steps, sequence analytics or workflow limits, so this reads as dependable task automation without an evidenced full builder. 5 6
The Skeptic
Real multi-step claims are published: event flows from invitation through participant management, certificates and follow-up, campaign automation for lead capture, data maintenance and communication, and a monitor that watches workflows in real time and distributes tasks automatically. We found no public information on branching, delays, sequence analytics or workflow caps, and with a separate catalogue of add-on modules, unpriced, it is impossible to tell which automation ships in the base product and which becomes an extra charge. 5 6 7
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
Over 100 named connections including ERP, DMS, Office 365 and DATEV, plus a web-connect product claiming automatic, seamless data flow between the CRM, websites and portals — a decent native directory on paper. We found no public information on email and calendar sync, documented API endpoints or limits, webhooks or OAuth apps, so the API half of the story is unverifiable. 5 6 7
The Data Protection Officer
The integration page names ERP, DMS, Office 365 and DATEV among over one hundred connectable systems, and a web connect product is described as moving data automatically between the CRM and websites, portals and other applications. We found no public information on API documentation, two-way email and calendar sync, webhooks or OAuth, so the directory is the evidenced strength. 4 5 7
The Sales Ops Lead
A native directory of over one hundred systems including ERP, DATEV and Office 365, plus an automatic web connect moving data between the CRM and external sites and portals, covers the finance stack I answer to. We found no public information on API documentation, rate limits, webhooks or two-way email and calendar sync. 4 5 7
The RevOps Integrator
The integrations page claims ERP, DMS, Office 365, DATEV and over 100 further systems, plus an automatic web connector — a directory that covers the German revenue stack, DATEV included. But we found no public information on API documentation, webhooks, OAuth apps, rate limits, or whether email and calendar sync is genuinely two-way rather than a one-way import in disguise. 7 5 6
The Migrator
More than one hundred connectable systems are named, including ERP, DMS, Office 365 and DATEV, alongside a web-connect bridge that moves data between the CRM, websites, portals and other applications. I found no public information on API documentation, rate limits, webhooks or OAuth applications, so external systems look first-class as a count but not as a documented contract — and an undocumented API is what turns an exit into a project. 5 7
The Skeptic
ERP, DMS, Office 365 and DATEV are named among connections to "über 100 weitere Systeme", and cobra CXM WEB CONNECT promises automatic data flow between the CRM, websites, portals and other applications. We found no public information on API documentation, rate limits, two-way email and calendar sync, webhooks or OAuth apps — the word API in the integration page's title is the only published trace of one. 5 7
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
A German entity under a German parent, a German cloud location, on-premise hosting in my own data center, order-processing agreements for the named EU hosts and an external data protection officer — this is the profile I want. It stops short of signoff because we found no public information on where cobra CRM Cloud customer data is hosted or on subprocessors for the CRM product itself, while Microsoft and Google stay in the chain with a US transfer the page says cannot be excluded — and the captured pages give different company names for the vendor, which I'd want settled first. 1 2 3
The Data Protection Officer
A German entity in Konstanz with 100% German development, an on-premise option in the customer's own data center, and EU-based website providers under Article 28 GDPR contracts is a genuinely European starting point. But the privacy policy does not state where cobra CRM Cloud customer data is hosted — the German cloud location appears only in homepage marketing — and no subprocessors are disclosed for the CRM Cloud product itself, with the page conceding a US transfer cannot be excluded for the engaged Google and Microsoft services. The published retention rules cover only website analytics and job applications; we found no public information on retention, deletion or consent fields for CRM records. 1 2 3
The Sales Ops Lead
A German entity, a German cloud location plus an on-premise option, an Art. 28 DPA, an external data protection officer and named EU hosting providers describe a European posture I could defend. The cloud location rests on homepage marketing, we found no public information on subprocessors for the CRM Cloud product itself, and the privacy policy names Google and Microsoft with a US transfer it says cannot be excluded. 1 2 3
The RevOps Integrator
A German entity with an on-premise option in the customer's own data center, a German cloud location, Art. 28 GDPR processing agreements, EU-based named hosts, and US exposure confined to named website services via DPF-certified Google and Microsoft, with the page itself noting a US transfer cannot be excluded. What a DPO would still want has no public information — a subprocessor list for the CRM cloud product itself, and retention or deletion controls for customer data — and the cloud location appears in marketing copy rather than the privacy policy. 1 2 3
The Migrator
A German entity under a German parent, cloud hosting claimed in Neunkirchen, an on-premise option in the customer's own data center, an external data protection officer, Article 28 processing agreements and all named website hosts inside the EU. Against that: the privacy policy does not state where the CRM Cloud customer data is hosted, no subprocessors are disclosed for the CRM Cloud product itself, Google and Microsoft remain a named residual US exposure via the Data Privacy Framework, and I found no public information on deletion or retention controls for CRM data itself. 1 2 3
The Skeptic
The entity is genuinely German — a GmbH in Konstanz under a German register court, parented from Neunkirchen — with an external data protection officer, processor agreements under Art. 28 GDPR, website hosting entirely with German, French and Slovenian providers, and a true on-premise option. But the German cloud location appears only in homepage marketing; the privacy policy is silent on where cobra CRM Cloud customer data is hosted, we found no subprocessor disclosure for the CRM product itself, and Google and Microsoft appear as EU-US Data Privacy Framework-certified processors where the page states a US transfer cannot be excluded. 1 2 3
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
We found no public information on import, export or migration on any captured page — no export formats, no documented path to pull my history out. The only data-movement evidence is a live-connection product for websites and portals, which is integration, not exit; as someone who prices the exit before the entrance, that silence decides the score. 5
The Data Protection Officer
Interfaces are mentioned and automatic data flow between the CRM and websites, portals and connected systems is described, but we found no public information on import tooling or export formats, and nothing on whether notes, activities and files can be taken out. Getting out of this database is entirely unevidenced. 5 6 7
The Sales Ops Lead
We found no public information on import, export or migration tooling — nothing on guided migration, full-object export or contractual data-return terms. The automatic connections to websites and over one hundred systems show data pathways, but an exit plan cannot be written from these pages. 5 6 7
The RevOps Integrator
We found no public information on import, export or migration tooling — nothing on CSV export scope, whether history or files come out, or API access sufficient to rebuild the database elsewhere. The only adjacent claims are automatic data flow through the web connector and 'interfaces', which describe integrations, not exit. 5 6
The Migrator
I found no public information on import tooling, export scope, guided migration or contractual data-return terms — the pages describe interfaces and a web-connect bridge that move data while you stay, but say nothing about getting your whole database, history and files out. For someone who prices the exit before signing, that absence is close to the floor. 5 7
The Skeptic
We found no public information on import, export, migration from competitors or contractual data-return terms on any captured page; the integration story is about connecting systems in, not getting data out. For a buyer, getting in and getting out are undocumented, which means both are sales conversations until proven otherwise. 1 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
The captured pages show not a single tier, seat price, billing period or renewal figure, and add-on modules are advertised with no numbers attached. A free cloud trial registration exists so I can at least try before talking to anyone, but I cannot compute any invoice from what is published — and unpriced modular add-ons are exactly where seat minimums hide. 2 7
The Data Protection Officer
The only public pricing facts are a self-serve free trial registration for cobra CRM Cloud and the statement that a comprehensive GDPR package is included free. We found no public prices for any tier, no per-seat figures, billing periods or VAT treatment, so a buyer cannot compute an invoice from the captured pages. 1 2
The Sales Ops Lead
The only pricing-adjacent fact captured is a free trial registration for the CRM Cloud product; we found no public prices for any tier, per-seat rates, billing periods, VAT treatment or renewal terms, and no public figures for the add-on modules. No buyer can compute a 40-seat invoice from these pages. 2 7
The RevOps Integrator
The only public, self-serve commercial artifact is a free trial registration for the cloud product; no price figures, tier structure, billing period split or VAT treatment appear on any captured page. Add-on modules are named without prices, so the real invoice cannot be computed from public pages at any seat count. 2 7
The Migrator
The only pricing-related fact I can confirm is a free registration for the Cloud product trial, while add-on modules are offered with no prices attached. No tier, seat price, billing period or renewal rule appears on the captured pages, so no real invoice can be computed from public information alone. 2 7
The Skeptic
Not one price figure appears on any captured page — no per-seat rates, no tiers, no billing periods, no VAT treatment of prices — only a free cloud trial and a catalogue of add-on modules advertised without figures. A buyer cannot compute any invoice from public pages, and an unpriced module catalogue is exactly where per-renewal surprises hide. 2 7
European sovereignty — proven facts
2 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 1 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 2 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. Cloud location appears only in homepage marketing copy; the privacy policy does not state where cobra CRM Cloud customer data is hosted, and the country is implied via Neunkirchen/Siegerland rather than spelled out.
- Weak sourcing — Subprocessors. Microsoft is contracted via its Irish EU subsidiary (Microsoft Ireland Operations Limited) while the page itself concedes a US transfer cannot be excluded, and no subprocessors are disclosed for the CRM Cloud product itself; the website hosts named (Raidboxes, Scaleway, domainfactory, BunnyWay) are all EU-based.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 7 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.cobra.de Checked 16 Sep 2026 Details →
- 2 Privacy policy www.cobra.de Checked 16 Sep 2026 Details →
- 3 Legal notice cobra.de Checked 21 Sep 2026 Details →
- 4 Pipeline & forecasting — found from sitemap cobra.de Checked 1 Oct 2026 Details →
- 5 Automation & workflows — found from sitemap cobra.de Checked 1 Oct 2026 Details →
- 6 Automation & workflows — found from sitemap cobra.de Checked 1 Oct 2026 Details →
- 7 Integrations & API — found from sitemap cobra.de Checked 1 Oct 2026 Details →