Software · head to head
June vs Countly
The short version
- Each has a real cost: June the pricing page lists a single all-in-one plan with no price, no minimum and no named cost driver; Countly the private cloud plan starts at $175 a month and is described as usage based without stating the unit
- They diverge on capability: June covers B2B analytics, Countly covers Event tracking.
Where they differ
Only the attributes on which June and Countly actually diverge.
Identical on both: starting price (Free), pricing model (freemium), free tier (Yes), user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in June
- B2B analytics
- Account tracking
- Cohort analysis
- Dashboards
- Slack
- Segment
- GDPR
- English language support
Only in Countly
- Event tracking
- Crash reporting
- Analytics dashboard
- User retention
- Open-source
- On-premise deployment
- Mobile support
- Api support
Both cover
- Cloud deployment
- Web support
What people use each for
The jobs each tool is most often brought in to do.
June
- Company-level product analytics for B2B SaaSnot Countly
- Spotting churn risk from account usage patternsnot Countly
- Pushing product usage data into Salesforce, HubSpot or Attionot Countly
Countly
- Product analytics for mobile and web applicationsnot June
- Self hosting analytics where data cannot leave the organisationnot June
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
June
- The pricing page lists a single all-in-one plan with no price, no minimum and no named cost driver
- There is no startup plan; the vendor states June is a fit for companies with at least $1M of ARR
- Setup fees are charged separately and the vendor states they vary based on implementation complexity
- The vendor states June is a poor fit for products with a large user base but low revenue per user
Countly
- The private cloud plan starts at $175 a month and is described as usage based without stating the unit
- No event cap, data point limit or user limit is published for either paid plan
- The self hosted Enterprise edition is custom priced and billed annually
- Adaptivity and intelligence features are separately priced add ons on the cheaper plan
Pricing, plan by plan
June
Free- FreeFree
- Basic analytics
- 1 user
- 30 days retention
Countly
Free- Open SourceFree
- Open-source
- Self-hosted
- Full features
Which should you pick?
Choose June if
- You need b2b analytics.
- You want to start without paying.
- You also want account tracking.
Choose Countly if
- You need event tracking.
- You want to start without paying.
- You work on Web, Mobile, Api.
- You also want crash reporting.
Questions people ask
- Is June or Countly better?
- Neither clearly leads. June starts at Free and Countly at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, June or Countly?
- June starts at Free and Countly at Free.
- Does June or Countly run on more platforms?
- June runs on Web. Countly runs on Web, Mobile, Api.
- Can I use June for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is June best used for?
- June is most often used for company-level product analytics for b2b saas, spotting churn risk from account usage patterns, pushing product usage data into salesforce, hubspot or attio. Of those, company-level product analytics for b2b saas and spotting churn risk from account usage patterns are not what Countly is typically brought in for.
- What can June do that Countly cannot?
- June covers B2B analytics, Account tracking, Cohort analysis, Dashboards. Countly covers Event tracking, Crash reporting, Analytics dashboard, User retention. Both handle Cloud deployment, Web support.