Countly

Mentioned, not specified.

Partially. On the trial question: yes — Countly's pricing FAQ states, "Yes. Countly Flex includes a 14-day free trial. Enterprise customers can request a live demo, and a demo environment is available for evaluating the platform." Flex (managed private cloud) starts at USD 175/month with usage-based pricing ("Pay monthly. Cancel anytime"), and Countly also publishes an open-source, self-hosted edition (linked to github.com/Countly) "suited to individual developers and small teams," which is the closest thing to a permanently free option. Countly Enterprise has no public price or trial — it is quote-based ("contact sales, no public list price") with a demo environment. On the second part of the question: the site does not state how many monthly events or tracked users the trial — or any tier — includes before you have to pay. Flex pricing is described only as "usage-based rather than per seat" with no published event/user allowance for the $175/month starting point or the 14-day trial, and no usage caps are given for the open-source edition.

Mentioned, not specified.

For Countly Flex, the site gives a specific answer: 'If you exceed your tier's monthly usage limit, your server access will be temporarily locked until the next cycle.' So on Flex, exceeding quota results in neither throttling nor overage billing — your entire server access is locked until the next billing cycle, and Countly recommends 'always upgrading to a tier that ensures uninterrupted access.' The chunks do not document what happens when quotas are exceeded on Countly Enterprise or Countly Lite — the pricing page content retrieved lists plans and capability suites but states no overage, throttling, or data-drop policy for them. The site also does not say whether events sent during a Flex lockout are queued, rejected, or dropped.

Mentioned, not specified.

Partly — and Countly's own FAQ hedges the 'out of the box' claim. On GDPR: the privacy-by-design FAQ says Countly provides 'first-party data collection, deployment control, consent management, access controls, and data-governance features that can help organizations meet GDPR requirements,' but explicitly states 'Compliance ultimately depends on each organization's implementation and use of the platform.' Marketing pages go further — Countly Lite claims a solution 'compliant with GDPR, COPPA, HIPAA, and other regulations,' the AI solutions page says it 'Meets GDPR, SCC, and HIPAA-ready standards from day one,' and GDPR is listed alongside ISO 27001/27017/27018, SOC 2 Type II, and HIPAA in its compliance badges. So: strong GDPR-supporting capabilities and certifications, but no unqualified 'GDPR compliant out of the box' guarantee — Countly itself frames compliance as dependent on your deployment and configuration. On region pinning: yes for self-hosted and private-cloud deployments — the FAQ states 'Self-hosted customers determine where their infrastructure and data reside, while private-cloud options can support organizational data-residency requirements,' and the financial-services page repeats 'deploy on your own servers or in a private cloud to ensure compliance with GDPR.' Countly even markets choosing local server providers inside Saudi Arabia for PDPL data residency. However, no chunk explicitly confirms an EU-hosted or EU-region-pinned option for Countly's own hosted cloud (Flex) — EU-specific pinning for their managed offering is not documented on these pages.

Mentioned, not specified.

The site confirms multi-app setups are a core concept but never states a numeric cap. Countly's support docs describe apps as 'the main grouping tool we have and they are used for data separation between your different projects,' and the features page lists a 'Consolidate' feature to 'bring data together from multiple apps to a single app' — so multiple apps under one account/deployment are supported. However, no retrieved page specifies how many apps are allowed per account or per tier (Lite/Flex/Enterprise). On quota: the closest item is the 'Data points' feature, which lets you 'track data point consumption in your Countly server,' implying quota accounting exists, but the site does not say whether that consumption is pooled across all apps or metered per app. Countly's own llms.txt states that 'https://countly.com/pricing is the authoritative source for current pricing and packaging,' so any app-count or quota limits would live there, but no pricing/limits page content was retrieved.

Mentioned, not specified.

Countly's website confirms that an SLA is included with the Enterprise plan — the plan comparison table shows "SLA: Optional" for Flex vs "SLA: ✓ Included" for Enterprise, and the pricing FAQ repeatedly lists "an included SLA" among Enterprise features (alongside a dedicated Customer Success Manager and tailored onboarding). However, the site nowhere states the actual uptime percentage guaranteed (e.g., 99.9%) or what compensation/service credits apply if the SLA is missed. Note also that Enterprise is self-hosted ("Deploy on your infrastructure", "Fully customer-owned & controlled"), and the site does not clarify what the SLA actually covers in that deployment model. To get the specific uptime commitment and remediation terms, you would need to request the SLA document via their demo/sales contact.

Mentioned, not specified.

Inclusion: the site answers this directly — per Countly's own llms.txt summary, "Cee is sold as a paid add-on on Countly Flex only. Countly Enterprise includes Cee as part of the plan, at no extra charge." The features page corroborates this by tagging the AI Agent Cee feature card as available on "enterprise flex" plans. Metering: the site does not explain how Cee usage is metered. No chunk specifies a metering unit (queries, seats, tokens, events) or rates for the Flex add-on — the llms.txt only says "See https://countly.com/pricing for current rates," and the retrieved pricing-page content contains no Cee metering details. For Enterprise, "at no extra charge" implies there is no separate usage-based billing, but the site never states an explicit metering policy (e.g., whether any usage caps apply). Cee is enabled per-server via Management > Feature Management > AI Assistants, which is an on/off toggle rather than a metering control.

Mentioned, not specified.

Countly's site confirms consent management at the platform level but does not document SDK-level, per-user consent enforcement or per-feature opt-outs. The privacy-by-design page states that "Granular permissions, consent management and audit logs give teams control over what is collected and who can see it" (countly.com/privacy-by-design), and the Enterprise FAQ says Countly's "deployment, access-control, consent, and data-management capabilities are designed to support requirements associated with regulations such as GDPR and HIPAA" (countly.com/enterprise). The SDK Hub also lists a dedicated "Privacy and Security" integration guide (support.count.ly article 21791284726428), and the mobile analytics FAQ notes that "Supported capabilities vary by SDK and can include analytics, user profiles, journeys, push notifications, crash reporting, experimentation, and feedback" (countly.com/solutions/mobile-analytics). However, none of the retrieved pages specify whether the SDKs expose per-user consent APIs or let you individually disable capabilities like crash reporting or location tracking for a given user. To confirm this, you would need to consult the "Privacy and Security" SDK integration guide directly, as its contents are not reproduced anywhere in the retrieved site pages.

Mentioned, not specified.

Mostly yes, with one gap. Countly's Enterprise page FAQ directly addresses this exact question — 'Does Countly support SSO and role-based access?' — and answers: 'Yes. Countly provides enterprise access controls, including configurable user roles and granular feature permissions. Administrators can control which applications and capabilities individual users can access and what actions they can perform.' The Enterprise plan is also listed on pricing as including 'All capabilities' with 'Enterprise-grade security & compliance.' Supporting this, Countly's site index lists 'single sign-on' among its privacy and governance capabilities (alongside enforced two-factor authentication and audit logging), and its User Management documentation describes managing user types such as global admin, admin, and user. The gap: nowhere on the retrieved pages does Countly name SAML specifically as the supported SSO protocol — the site says 'SSO' without specifying SAML 2.0 vs. OIDC or other protocols. Role-based access control is fully confirmed; SAML specifically is not, so if your identity provider requires SAML 2.0, verify that with Countly before committing.

Mentioned, not specified.

Countly's website does not publish any guaranteed support response time for Enterprise — no SLA response-time figures (e.g., '1 hour for P1') appear anywhere in the retrieved pages. On 24/7 coverage: the Enterprise page lists '24/7 support' as an Enterprise benefit, but only inside a decorative hero graphic (alongside 'Full ownership', 'Custom roles', 'Self-hosted or private cloud'), and it is not scoped to critical issues. The Enterprise page's 'Fast, expert support' section describes 'continuous assistance to resolve issues and keep your operations running smoothly', professional training, and proactive system monitoring with a dedicated account manager; the pricing page lists 'Dedicated CSM onboarding & support' for Enterprise. So: 24/7 support is claimed as a marketing bullet, but a contractual response-time guarantee and critical-issue coverage details are not stated — a buyer would need to contact sales to confirm SLA terms.

Mentioned, not specified.

Partially. The site confirms raw data export is a supported capability, but the retrieved pages never mention BigQuery, Snowflake, or any warehouse destination, nor do they state export formats or whether a streaming (continuous) export exists. What the chunks do establish: (1) Countly's support hub links a dedicated article, 'Exporting Data from Countly' (support.countly.com/hc/en-us/articles/900005403223), and a 'Working with Data' section described as covering 'Exporting, Purging Data and Database Schema Information'; (2) the Database viewer feature lets you 'Browse Countly databases from the user interface or via the REST API', and Countly publishes Read and Write API documentation; (3) Countly documents its underlying MongoDB database schema (e.g., countly.eventTimes{ID}, countly.app_users{ID}), implying direct access to raw event collections; (4) marketing pages claim data is 'instantly queryable and exportable' and that Countly operates as data infrastructure where data is 'routed across internal systems, analytics workflows, and AI-driven use cases.' Note that 'stream ingestion' on the site refers to ingesting data INTO Countly, not streaming it out. So: export and raw-data API access clearly exist, but whether there is a managed pipeline to BigQuery/Snowflake and in what format (CSV, JSON, etc.) is not answered by the retrieved content — those specifics likely live in the Exporting Data article, whose body was not captured.

Mentioned, not specified.

Countly's site does not publish a specific rate limit (requests per second) for its event ingestion API. The closest data points the site offers are capacity and scalability claims, not enforced limits: the Countly Implementation and Technical FAQ states "A high-end server can handle several hundreds of events per second" — a self-hosted hardware-capacity figure, not an API cap — and marketing pages claim Countly "uses stream ingestion and columnar storage, enabling scalable, high throughput analytics" and is "designed to operate at very high event volumes." Nothing in the retrieved content documents a hard req/s threshold, throttling/429 behavior, or what happens during traffic spikes. For self-hosted deployments, ingestion throughput appears bounded only by server hardware; for Countly-hosted editions (Flex/Lite), no published ingestion rate limit was found in these chunks.