Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Opencom

an open-source Intercom alternative given the Salesforce deal

Details

External ID
48552549
Source
HN
Company
—
Product
Opencom
Website domain
opencom.dev
Launched
June 16, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.12568306010928962
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

I built Opencom, an open-source alternative to Intercom for customer support chat, with knowledge-base and AI support, and mobile apps for push notifications etc.It includes a web widget, agent inbox, customer/company profiles, conversations, realtime messaging, AI support and a live demo. The aim is to provide a simple, self-hostable foundation for teams that want Intercom support without being locked into a large SaaS platform.Salesforce has just announced its acquisition of Fin, formerly Intercom, for around $3.6bn. Customer communication is important infrastructure, and I think there should be a credible open-source option.Built with TS, NextJS, React Native & Expo, and Convex backend for easy setup and ability for full self-hosting. Repo: https://github.com/opencom-org/opencom.Appreciate any feedback on architecture, self-hosting setup, and which Intercom-style features people would want before using it in production, along with any other thoughts.It is entirely OSS - no paid features behind a paywall. I hope this could become a community project.

Enrichment

Theme
niche social and community platforms
Vertical
Horizontal
Function
Communication
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
open-source customer messaging platform
Manually corrected
False

Could you build this?

Partial Building a basic customer chat widget with RAG capabilities is manageable, but creating a full-scale Intercom replacement requires robust multi-tenant real-time messaging, ticketing state machines, and multi-channel synchronization.

What it would actually take: A production version requires an event-driven architecture using WebSockets/SSE (e.g., Elixir/Phoenix or Node/Go with Redis Pub/Sub), PostgreSQL for durable conversation histories, and vector search (pgvector) for the RAG agent. Hard parts include reliable bi-directional email syncing (handling MIME complexities, threading headers, spam filters) and high-throughput real-time deliverability across web and mobile push notifications. It demands skilled backend and infrastructure engineering to maintain sub-second latency and zero message loss.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 29 launches clear the similarity bar, closest 8 shown.

Attention rank: #26 of 30 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 228 days after the earliest competitor.

Other launches for this product