June.so

Name: June.so
Brand: June.so
Rating: 5 (41 reviews)

AI Native

The new way to do product analytics (YC W21

Est 2020|Valuation $1.8M|Raised $2.5M

LinkedIn 9K|Web traffic 13K|FTEs 8|HQ San Francisco, California, US

MarketsWeb & Product Analytics

01Common complaints

- Any scenario today (post-shutdown) - As of 2026, June is not available for new purchases because it shut down on **August 8, 2025**; organizations should not select June as a primary analytics vendor for new deployments. - If evaluating historically (pre-shutdown) - Enterprises requiring documented SOC 2 / ISO certifications, SSO/SCIM support, or strict audit trails. - Teams needing advanced experimentation platforms, large-scale behavioral analytics modules, or extensive ecosystem tooling, where providers such as Amplitude or Mixpanel typically had more mature feature sets. - Budget-constrained startups that relied on a free tier; community reports indicated that removal of a free plan affected some early-stage teams. - Current limitations acknowledged by vendor - The primary limitation for any prospective buyer is that June shut down on **August 8, 2025** and provided migration guidance to Amplitude. - Security/compliance gaps (publicly documented) - No explicit SOC 2 or ISO certification statements were located in the public help-center materials reviewed. - Roadmap / future - June no longer operates as an independent product; public materials focus on migration and mapping to Amplitude rather than independent product roadmap items. - Data portability / migration - June published migration guidance for exporting data and mapping June features to Amplitude, including notes about regional workspace constraints in Amplitude.

03Field reports

Note: Since June ceased operating in August 2025, most reviews are historical. Major enterprise review platforms had limited or no listings for June at the time of this review. - Review platforms (G2) — limited volume - G2 showed a small number of reviews and an auto-generated pros/cons summary. The low review count limits confidence in generalizing reviewer sentiment. - Themes observed in the available reviews included reports of responsive customer support and descriptions of a user interface that some reviewers found straightforward; these observations came from a very small sample. - Community/Social (Reddit / HackerNews / YC subreddit signals) - Community threads referenced June as a simplified product analytics alternative to larger suites. - Several community posts documented concerns about the removal of a free plan and later the acquisition and shutdown, which drove migration activity. - Direct quotes (examples) - From June’s CEO on Reddit (community post introducing an analytics education thread): "Enzo speaking, CEO of June.so." - From a community user describing switching pressure: "Used June.so … until they killed their free plan … Now considering our options, as June’s published pricing increased." - From a migration tooling post: "June.so was acquired by Amplitude and the tool will stop functioning on a specified shutdown date." - Reasons cited for selecting June historically - Preference for a simpler, preconfigured approach to B2B/product analytics compared with more complex analytics suites. - Interest in company/account-level analytics and PLG-to-CRM synchronization. - Reasons for customer churn or migration - Pricing changes and removal of a free plan, as reported in community discussions. - The acquisition and shutdown required migration for remaining customers.

Vendor / partner case-study style content located

Attio published partner content describing a June integration and use of Attio custom objects.

Critical evaluation

Available case-style content is primarily vendor or partner narratives and lacks independent, audited ROI or counterfactual analysis. Methodologies and measurable outcomes are not transparently documented in the public materials reviewed.

Migration as an operational case

June published migration guidance mapping June features into Amplitude and noting regional workspace differences. The shutdown created a practical migration use case for customers and highlighted workstreams required for continuity (export, mapping, and reimplementation).

04Best fit

Note: Because June shut down, the ICP below describes who June was designed for historically, rather than a current vendor recommendation. - Company sizes - Historically, June appeared to fit small-to-mid B2B SaaS teams without a dedicated analytics engineering function that needed account-level insights. - Industries - Primarily B2B SaaS (horizontal), especially teams operating PLG motions where mapping product events to CRM objects is relevant. - Roles and personas - Decision makers: Head of Product, Growth lead, VP Marketing (PLG), RevOps/GTMOps - End users: Product managers, designers, growth analysts, founders - Pain points addressed - Providing company-oriented product analytics without building a warehouse-first stack. - Offering a set of preconfigured metrics for activation and retention that reduced initial configuration effort. - Deal disqualifiers (historical and current) - Current: any new purchase — June is not available as an ongoing product following the shutdown. - Historical: teams that required formal security/compliance certifications, SSO/SCIM support, deep auditability, advanced experimentation, session replay, or broader enterprise tooling.

05The pitch

What the product does (core value proposition in objective terms)

- June marketed itself as a B2B SaaS-focused product analytics platform that provided a set of preconfigured product metrics out of the box (examples: active users, power users, new users, retention) and integrated those metrics into collaboration and workflow tools such as Slack and Notion. - June also included company/account-level analytics, and offered integrations to CRMs (Salesforce, HubSpot, Attio) and Stripe to provide revenue context alongside product usage data. - In 2025, June announced it was joining Amplitude and published a shutdown date; following that announcement June became primarily relevant as a legacy system and migration source rather than an active vendor.

Target market and market positioning

Targeted primarily at B2B SaaS teams seeking a simpler setup and preconfigured default reporting compared with more customizable analytics suites.
Emphasized product-led growth (PLG) workflows and synchronizing product usage data into CRM systems (notably Attio).

01Common complaints

Any scenario today (post-shutdown)
- As of 2026, June is not available for new purchases because it shut down on August 8, 2025; organizations should not select June as a primary analytics vendor for new deployments.
If evaluating historically (pre-shutdown)
- Enterprises requiring documented SOC 2 / ISO certifications, SSO/SCIM support, or strict audit trails.
- Teams needing advanced experimentation platforms, large-scale behavioral analytics modules, or extensive ecosystem tooling, where providers such as Amplitude or Mixpanel typically had more mature feature sets.
- Budget-constrained startups that relied on a free tier; community reports indicated that removal of a free plan affected some early-stage teams.
Current limitations acknowledged by vendor
- The primary limitation for any prospective buyer is that June shut down on August 8, 2025 and provided migration guidance to Amplitude.
Security/compliance gaps (publicly documented)
- No explicit SOC 2 or ISO certification statements were located in the public help-center materials reviewed.
Roadmap / future
- June no longer operates as an independent product; public materials focus on migration and mapping to Amplitude rather than independent product roadmap items.
Data portability / migration
- June published migration guidance for exporting data and mapping June features to Amplitude, including notes about regional workspace constraints in Amplitude.

03Field reports

Note: Since June ceased operating in August 2025, most reviews are historical. Major enterprise review platforms had limited or no listings for June at the time of this review.

Review platforms (G2) — limited volume
- G2 showed a small number of reviews and an auto-generated pros/cons summary. The low review count limits confidence in generalizing reviewer sentiment.
- Themes observed in the available reviews included reports of responsive customer support and descriptions of a user interface that some reviewers found straightforward; these observations came from a very small sample.
Community/Social (Reddit / HackerNews / YC subreddit signals)
- Community threads referenced June as a simplified product analytics alternative to larger suites.
- Several community posts documented concerns about the removal of a free plan and later the acquisition and shutdown, which drove migration activity.
Direct quotes (examples)
- From June’s CEO on Reddit (community post introducing an analytics education thread): "Enzo speaking, CEO of June.so."
- From a community user describing switching pressure: "Used June.so … until they killed their free plan … Now considering our options, as June’s published pricing increased."
- From a migration tooling post: "June.so was acquired by Amplitude and the tool will stop functioning on a specified shutdown date."
Reasons cited for selecting June historically
- Preference for a simpler, preconfigured approach to B2B/product analytics compared with more complex analytics suites.
- Interest in company/account-level analytics and PLG-to-CRM synchronization.
Reasons for customer churn or migration
- Pricing changes and removal of a free plan, as reported in community discussions.
- The acquisition and shutdown required migration for remaining customers.

Vendor / partner case-study style content located

Attio published partner content describing a June integration and use of Attio custom objects.

Critical evaluation

Available case-style content is primarily vendor or partner narratives and lacks independent, audited ROI or counterfactual analysis. Methodologies and measurable outcomes are not transparently documented in the public materials reviewed.

Migration as an operational case

June published migration guidance mapping June features into Amplitude and noting regional workspace differences. The shutdown created a practical migration use case for customers and highlighted workstreams required for continuity (export, mapping, and reimplementation).

04Best fit

Note: Because June shut down, the ICP below describes who June was designed for historically, rather than a current vendor recommendation.

Company sizes
- Historically, June appeared to fit small-to-mid B2B SaaS teams without a dedicated analytics engineering function that needed account-level insights.
Industries
- Primarily B2B SaaS (horizontal), especially teams operating PLG motions where mapping product events to CRM objects is relevant.
Roles and personas
- Decision makers: Head of Product, Growth lead, VP Marketing (PLG), RevOps/GTMOps
- End users: Product managers, designers, growth analysts, founders
Pain points addressed
- Providing company-oriented product analytics without building a warehouse-first stack.
- Offering a set of preconfigured metrics for activation and retention that reduced initial configuration effort.
Deal disqualifiers (historical and current)
- Current: any new purchase — June is not available as an ongoing product following the shutdown.
- Historical: teams that required formal security/compliance certifications, SSO/SCIM support, deep auditability, advanced experimentation, session replay, or broader enterprise tooling.

05The pitch

What the product does (core value proposition in objective terms)

June marketed itself as a B2B SaaS-focused product analytics platform that provided a set of preconfigured product metrics out of the box (examples: active users, power users, new users, retention) and integrated those metrics into collaboration and workflow tools such as Slack and Notion.
June also included company/account-level analytics, and offered integrations to CRMs (Salesforce, HubSpot, Attio) and Stripe to provide revenue context alongside product usage data.
In 2025, June announced it was joining Amplitude and published a shutdown date; following that announcement June became primarily relevant as a legacy system and migration source rather than an active vendor.

Target market and market positioning

Targeted primarily at B2B SaaS teams seeking a simpler setup and preconfigured default reporting compared with more customizable analytics suites.
Emphasized product-led growth (PLG) workflows and synchronizing product usage data into CRM systems (notably Attio).

June.so

01Common complaints

02Why they buy

03Field reports

Vendor / partner case-study style content located

Critical evaluation

Migration as an operational case

04Best fit

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning

01Common complaints

02Why they buy

03Field reports

Vendor / partner case-study style content located

Critical evaluation

Migration as an operational case

04Best fit

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning