From Forum to Social Network: The Origin Story of Cometbid Social

01It Started with a Forum

The Cometbid Technology Foundation was built around open-source projects. And open-source projects need a place to talk — about bugs, features, architecture decisions, and roadmaps. The natural answer was a forum.

We wanted a global forum for the open-source community. A place where contributors from different countries, different time zones, and different projects could come together and have meaningful conversations. Not a Slack channel that scrolls away. Not a GitHub issue thread buried under CI logs. A proper, persistent, searchable forum where knowledge accumulates over time.

So we started building one. The plan was straightforward: discussion threads organized by project, categories for different topics, upvoting, tagging, and moderation tools. A classic forum, built on modern infrastructure.

💬

The original vision was simple: give the open-source community a persistent, searchable place to talk. No chat noise. No disappearing messages.

02The Problem with Technical-Only Spaces

As the forum took shape, a concern kept growing. In an open-source forum, what do people talk about? Code. Architecture. Pull requests. Deployment strategies. Debugging sessions.

That is great for developers. But it alienates everyone else.

Open-source projects are not just code. They involve designers who create the interfaces, project managers who coordinate releases, technical writers who document the APIs, community managers who onboard new contributors, and users who report bugs and suggest features. These people are essential to any project's success, but a forum dominated by technical discussions makes them feel like outsiders.

We did not want to build a space where only the most technical voices were heard. We wanted a platform where a designer could share a UI concept and get feedback. Where a project manager could post a roadmap update and start a discussion. Where a first-time contributor could ask a basic question without feeling out of place.

A traditional forum, by its nature, gravitates toward the technical. The threading model, the category structure, the culture — it all favors depth over breadth. And depth, in open-source, usually means code.

🎯

Open-source is not just code. Designers, writers, project managers, and community builders are just as important — but technical forums push them to the margins.

03The Pivot: Two Platforms, One Codebase

The realization came in February 2026. We were deep into the forum backend — DynamoDB tables, API routes, moderation tools — when we stepped back and asked: what if we built both?

What if cometbid.org kept its forum? A focused, technical space for open-source project discussions. Threaded conversations, code snippets, project-specific categories. The kind of place where a maintainer can post an RFC and get detailed technical feedback.

And what if we used the same codebase to build something broader? A social networking platform — cometbid.com — where the conversation is not limited to code. Where you can share a post, follow people, react, comment, and build a professional network. Where the barrier to participation is not technical knowledge but simply having something to say.

The architecture supported it. The social network backend we were building — profiles, connections, posts, reactions, activity feeds — could serve both use cases. The forum is a specialized view of the same underlying data model. A forum thread is a post with structured replies. A forum category is a topic filter. The difference is in the presentation and the culture, not the infrastructure.

So we pivoted. Not away from the forum, but toward something bigger. Two platforms, one codebase, two audiences.

🔀

February 2026 was the pivot month. We did not abandon the forum — we expanded the vision. Two platforms, one codebase: cometbid.org for technical discussions, cometbid.com for everyone.

04cometbid.org: The Open-Source Forum

The forum at cometbid.org remains the home for technical open-source discussions. It is where maintainers post RFCs, contributors discuss implementation details, and users report issues in a structured format.

Forums are organized by project. Each TCTF project gets its own space with categories for announcements, feature requests, bug reports, and general discussion. Threading keeps conversations focused. Code formatting, syntax highlighting, and inline diffs make technical discussions readable.

This is the space for depth. Long-form technical posts, architecture decision records, and detailed Q&A threads. The audience is developers, maintainers, and technical contributors who want a persistent, searchable knowledge base for the projects they work on.

05cometbid.com: Cometbid Social

Cometbid Social at cometbid.com is the broader platform. It is a professional social network for the global tech community — not just developers, but everyone who works in and around technology.

The feed is not filtered by technical depth. A designer can share a portfolio piece. A project manager can post about a successful release. A student can ask for career advice. A community builder can announce an event. The content is diverse because the audience is diverse.

Profiles on Cometbid Social are professional identities. Skills, experience, achievements, and connections — all in one place. The platform supports posts, reactions, comments, shares, messaging, and project collaboration. It is where you build your professional network in the tech community.

The key difference from the forum is accessibility. You do not need to understand DynamoDB single-table design to participate. You just need to be part of the tech community — in any role, at any level.

🌍

Cometbid Social is for everyone in tech — not just the people who write the code, but the people who design it, manage it, document it, and use it.

06Same Codebase, Different Experiences

Under the hood, both platforms share the same backend infrastructure. The social network service (cdk-social-network) handles profiles, connections, posts, and reactions for both. The activity service (cdk-activity-service) powers notifications and feeds for both. The authentication stack is shared. The messaging system is shared.

What differs is the frontend experience. cometbid.org presents content in a forum layout — threaded discussions, project categories, technical formatting. cometbid.com presents content in a social feed — posts, reactions, profiles, and discovery.

This shared-codebase approach means features built for one platform benefit the other. When we improve search on Cometbid Social, forum search gets better too. When we add moderation tools for the forum, Cometbid Social gets them as well. The investment compounds.

It also means we can ship faster. Instead of maintaining two separate backends, we maintain one — with two frontend experiences that serve different audiences and different use cases.

07What This Means Going Forward

The pivot from forum to forum-plus-social-network shaped the entire 2026 roadmap. The social network backend that shipped in February was not just for Cometbid Social — it was the foundation for both platforms.

In the months ahead, you will see both platforms evolve. The forum will get richer threading, better code formatting, and project-specific workflows. Cometbid Social will get messaging, project collaboration, billing, and a mobile app.

But the origin story matters because it explains why we built what we built. We did not set out to create another social network. We set out to give the open-source community a voice — and realized that voice needed to be louder, broader, and more inclusive than a forum alone could provide.

🚀

We did not set out to build a social network. We set out to give the open-source community a voice — and realized that voice needed to include everyone.