JENTIS vs Pulse by Ciphera

Compare JENTIS y Pulse by Ciphera en capacidades, jurisdicción, garantías y encaje para compradores europeos.

Ambos figuran como alternativas a: Google Analytics

JENTIS

Austria· Web Analytics

Needs review

Shortlist when you need managed server-side / first-party capture with EU-entity hosting and multi-destination activation (ads + analytics). Skip when you only want lightweight privacy analytics or free self-hosted tagging—consider Piwik PRO or etracker for EU analytics-first stacks, or Google sGTM if you will operate a Google-centric pipeline yourself.

EU-operated (Austria)Server-side tag managerEU/EEA hosting (claimed)ISO 27001 (claimed)Managed SaaSNot open source

Ver ficha Visitar sitio web

Pulse by Ciphera

Belgium· Web Analytics

Needs review

Shortlist Pulse when you want cookieless traffic analytics plus uptime and Lighthouse in one Belgian-operated, Swiss-hosted SaaS and can accept a closed managed backend. Skip when you need full self-hosting or GA-style user-level history; consider Plausible Analytics or Simple Analytics instead.

EU-operatedCookielessOpen-source clientSwiss-hosted dataNo analytics cookies

Ver ficha Visitar sitio web

Las filas resaltadas diferencian a los dos productos.

JENTIS vs Pulse by Ciphera: Resumen
Característica	JENTIS	Pulse by Ciphera
País de origen	Austria	Belgium
Categoría	Web Analytics	Web Analytics
Código abierto	No	Sí
Autoalojado	No	No
Sede	Austria	Belgium
Entidad legal	JENTIS GmbH	Ciphera BV
Ley aplicable	Austria / EU GDPR	Belgian law (GDPR); Swiss FADP for infrastructure location
Matriz / control EE.UU.	Sin matriz estadounidense conocida	Sin matriz estadounidense conocida
Exposición CLOUD Act (indicativa)	Bajo	Bajo
Estado de alojamiento en la UE	No indicado	Parcial
Alojamiento / residencia	Product: default EU/EEA-only processing on ISO 27001-certified cloud; docs cite IONOS cloud (Germany/EU). Exact host/region named in customer DPA. Optional non-EU instances may add non-EU subprocessors if selected. Marketing website separately uses Host Europe (DE) and US SaaS (HubSpot, Salesforce, Google) for corporate CRM/ads—not the Twin Server product path.	Primary compute and object storage on Exoscale in Switzerland (Zurich). Encrypted backups and domain registration via Infomaniak (Switzerland). CDN/DNS/DDoS via Bunny (Slovenia HQ, global edge for transient IPs). Payments via Mollie (Netherlands). GitHub (US) for public source code only, per Trust page.
Resumen	Austrian managed server-side data capture and hybrid tag manager: first-party Twin Server collection, consent-aware routing, and ad activation for multi-tool MarTech stacks.	Cookie-free web analytics with traffic, funnels, uptime and Lighthouse checks in one Belgian-operated, Swiss-hosted dashboard.
Etiquetas	gdpr server-side-tracking tag-management first-party-data martech austria	gdpr privacy cookie-free web-analytics open-source cookieless

De un vistazo: JENTIS vs Pulse by Ciphera
De un vistazo	JENTIS	Pulse by Ciphera
HQ	Vienna, Austria	Diegem, Belgium (Ciphera BV)
Legal entity	JENTIS GmbH (FN 529675i)	Ciphera BV (KBO/BCE 1013.721.660)
Founded	2020	18 September 2024 (CBE)
Product type	Managed server-side data capture / hybrid tag manager	No indicado
Hosting model	Managed SaaS; EU/EEA by default (IONOS cited in docs)	No indicado
Open source	No	No indicado
Self-hosted product	No (managed hosting)	No indicado
Commercial model	Sales-led SaaS (demo / consultation)	Free Hobby tier; paid plans by traffic scale
Primary data region	No indicado	Switzerland (Exoscale Zurich)
License	No indicado	AGPL-3.0 client; managed backend closed
Cookieless	No indicado	Yes (vendor claim: no cookies, no fingerprinting)
Data residency regions	No indicado	Switzerland (Exoscale primary; Infomaniak backups)

Key capabilities: JENTIS vs Pulse by Ciphera
Key capabilities	JENTIS	Pulse by Ciphera
EU-operated (Austria)	Sí	Sí
Server-side tag manager	Sí	No indicado
EU/EEA hosting (claimed)	Sí	No indicado
ISO 27001 (claimed)	Sí	No indicado
Managed SaaS	Sí	No indicado
Not open source	Sí	No indicado
Cookieless	No indicado	Sí
Open-source client	No indicado	Sí
Swiss-hosted data	No indicado	Sí
No analytics cookies	No indicado	Sí

JENTIS

Hybrid server-side tag management
One container for client- and server-side tags with first-party DNS; migrate data-layer logic and debug from browser hit to server dispatch without running your own sGTM fleet.
Twin Server capture and transforms
Server-side session mirror that can pseudonymize, anonymize, enrich, and time-frame parameters before forwarding—usable as a CNIL-style proxy pattern when configured carefully.
Essential Mode for non-consent traffic
Configurable minimized/anonymized capture when marketing consent is refused so sessions and conversions are not fully invisible—subject to DPO/legal sign-off per jurisdiction.
Synthetic Users for ad activation
Models trained on consented first-party data produce synthetic conversion signals for Google, Meta, TikTok, and other ad APIs; measure impact with holdouts—legal basis is configuration-specific.
Managed EU connectors and raw export
Vendor-maintained connectors across analytics, ads, and MarTech plus raw data export/API-style control; not a self-hosted open-source stack.

Pulse by Ciphera

Cookieless traffic dashboard
Pageviews, unique-visitor estimates, referrers, UTM campaigns, device or browser splits, and country-level geo from a single script tag, without cookies or fingerprinting according to Ciphera's privacy docs.
Journeys and conversion funnels
Step-by-step path columns and multi-step funnels with drop-off analysis, filterable by page, country, device, or referrer for privacy-preserving conversion debugging.
Uptime monitors with alert routes
Built-in uptime checks with downtime and recovery alerts to email, Slack, Discord, or a webhook, so availability sits beside traffic in one console.
Daily Lighthouse and Core Web Vitals
Scheduled mobile and desktop Lighthouse runs with performance, accessibility, best-practices, SEO scores, and Core Web Vitals trends without a separate RUM product.
Inspectable AGPL client and read API
Dashboard and tracking script are AGPL-3.0 on GitHub; Ciphera also documents a public read API, CLI, and export paths while keeping the managed backend closed.

Assurance & compliance: JENTIS vs Pulse by Ciphera
Assurance & compliance	JENTIS	Pulse by Ciphera
Independent security / no-logs audit	Not found No public independent no-logs or third-party security audit PDF located; ISO is the main public assurance claim.	Not found Trust page states no independent audit yet; Tessera self-audit published; independent audit planned.
ISO 27001	Vendor claimed Vendor states ISO 27001 / ISO 27001:2013 certification on site footer and privacy docs; certificate not independently verified in this draft.	Not found Ciphera explicitly states it holds no ISO 27001 certification.
SOC 2 / SOC 3	Not found No public SOC 2/3 report found on marketing or privacy docs.	Not found Ciphera explicitly states it holds no SOC 2 certification.
GDPR / EU data protection	Vendor claimed Austrian controller entity; product marketed as privacy-by-design processor with EU hosting, CMP hooks, and transform functions. Not legal advice—confirm config and DPA.	Vendor claimed Belgian controller; privacy policy describes GDPR/FADP bases and Pulse processor role. Not legal advice.
US CLOUD Act exposure (indicative)	Partial EuropeanStack assessment: AT entity and no known US parent; product hosting claimed EU-only (e.g. IONOS). Residual exposure via customer-chosen US destinations and any non-EU instance option. Not legal advice.	Partial EU (Belgian) entity with no known US parent; primary hosts are European (Exoscale, Infomaniak, Bunny, Mollie). Residual paths: GitHub (US) for source code only; Bunny global edge for transient IPs. Indicative only, not legal advice.
Data processing agreement (B2B)	Vendor claimed Sample DPA via Customer Legal Hub; required for SaaS processing. Confirm signed version and subprocessor annex.	On request / NDA Privacy policy: DPA available on request at privacy@ciphera.net for Pulse processor relationships.
EU AI Act	Not applicable Core product is tag/data capture; Synthetic Users is ML-assisted but product is not marketed as a general-purpose AI system. Revisit if Synthetic Users becomes a primary regulated AI offering.	Not applicable Web analytics product; not an AI system product page.

Considerations & known limitations: JENTIS vs Pulse by Ciphera
Considerations & known limitations	JENTIS	Pulse by Ciphera
Consent modes need legal sign-off	High Essential Mode and Synthetic Users can re-open measurement when users refuse cookies; legality depends on jurisdiction, configuration, and DPO assessment—not automatic compliance.	No indicado
Downstream US ad/analytics tools	Medium Even with EU capture, enabling Google/Meta/TikTok connectors can transfer personal data to US providers; use transforms/proxy patterns and transfer tools as required.	No indicado
ISO claimed; limited public audits	Medium ISO 27001 is vendor-asserted; no independent public security/no-logs audit found. Request certificate, pen-test summaries, and full subprocessor list under NDA if needed.	No indicado
Managed SaaS, not self-host	Medium No open-source self-host product path; ops simplicity trades for vendor dependency, sales-led pricing, and migration cost if you later leave.	No indicado
Implementation and data-layer effort	Low Migration from client-side tags still needs DNS, data layer, CMP mapping, and QA—vendor connectors reduce but do not eliminate engineering work.	No indicado
Managed backend is not open source	No indicado	Medium You can audit the browser script and dashboard code, but not the operated ingestion and storage service. Procurement that requires full-stack self-host or full server auditability should look elsewhere.
No ISO/SOC or independent audit yet	No indicado	Medium Ciphera publishes threat models, a warrant canary, and a subprocessor list, but explicitly has no ISO 27001 or SOC 2 and no completed independent audit. Enterprise security reviews will need questionnaires and a signed DPA.
Primary data residency is Switzerland, not EU/EEA	No indicado	Low Swiss adequacy covers many GDPR transfer questions, but policies that hard-require EU/EEA datacenter soil will classify this as partial rather than EU-hosted.
Marketing vs privacy wording conflicts	No indicado	Low Product FAQ pages disagree on whether custom events ship today and whether a DPA is needed. Prefer privacy@ and the privacy policy for legal commitments until Ciphera aligns the FAQs.

Encaje

JENTIS

Best fit when

E-commerce and multi-brand sites that lose conversion data to blockers, ITP, and consent drop-off
Performance marketing teams activating into Google, Meta, TikTok, and other ad APIs from first-party events
Analytics/DPO pairs that need data-point-level governance, CMP sync, and pseudonymization before third-country tools
Organizations preferring a managed EU capture layer over self-operated server-side GTM
Stacks that feed both EU analytics (e.g. Piwik PRO) and global ad platforms from one collection path

Poor fit when

Teams seeking free, open-source, or fully self-hosted analytics only
Lightweight privacy page analytics without ad activation or hybrid tag management
Buyers who cannot run sales-led procurement, data-layer work, and legal review of consent modes
Use cases that need a full CDP/BI product rather than capture and routing

Consider instead when

When: You primarily need EU privacy-focused web analytics (and optional self-host), not multi-destination ad activation
Consider: Piwik PRO or etracker
JENTIS can still sit in front of Piwik PRO; choose the analytics product when capture is not the bottleneck.
When: You are Google-only and will operate server-side GTM yourself
Consider: Google Tag Manager (server-side) + GA4
Lower cash cost; higher ops burden and different transfer/jurisdiction posture.
When: You need a full customer data platform or enterprise analytics suite
Consider: Adobe Analytics or a dedicated CDP (e.g. Tealium)
JENTIS is capture/routing at the start of the chain, not a CDP replacement.

Pulse by Ciphera

Best fit when

EU or Swiss organisations replacing GA4 primarily to remove analytics cookies and consent-banner friction
Teams that want traffic, funnels, uptime, and Lighthouse scores in one vendor console
Buyers who need a Belgian legal entity and named European subprocessors rather than a US cookieless SaaS
Sites that can work with aggregate and month-scoped visitor estimates instead of persistent user IDs
Engineering leads who want the browser script and dashboard code on GitHub under AGPL-3.0 for inspection

Poor fit when

Organisations that must self-host the full analytics backend (Pulse's managed core is closed)
Product analytics use cases that need durable cross-visit identity, cohorting, or GA4 BigQuery-style user exports
Buyers requiring completed ISO 27001, SOC 2, or a published independent security audit today
Teams that need EU/EEA soil specifically rather than Swiss residency (primary data is in Switzerland)

Consider instead when

When: You need a mature EU cookieless analytics product with an official full-stack self-host option
Consider: Plausible Analytics
Plausible (Estonia) is the common self-host plus SaaS peer; Pulse keeps the backend managed-only.
When: You want a minimal Dutch cookieless counter without uptime or Lighthouse bundles
Consider: Simple Analytics
Closer peer for strictly analytics SaaS; Pulse differentiates with ops-style panels.
When: You need enterprise analytics with strong EU residency controls and heavier compliance packaging
Consider: Piwik PRO or Friendly Analytics
Heavier Matomo-class or Swiss-hosted peers when Pulse's startup assurance set is too thin.

Open questions for due diligence

JENTIS

What is the exact production cloud provider, region, and subprocessor list on the current DPA annex?
Can the vendor produce a current ISO 27001 certificate and any independent penetration-test summary?
Has legal counsel approved Essential Mode and Synthetic Users for your markets (ePrivacy/GDPR basis)?
Which destinations will receive personal data vs pseudonymized/synthetic signals only?
What SLA, raw data retention, and exit/export terms apply to your tier?

Pulse by Ciphera

Will Ciphera sign your standard DPA and return the full registered-address subprocessor appendix on request?
What is the retention and deletion SLA for a single customer's Pulse project data after contract end?
When is the planned independent security audit scheduled, and will the report be public?
Are Google Search Console, Bing, or CDN analytics panels generally available, or only mentioned in some marketing copy?