
Our quarterly roadmap for Q2 — what shipped in April, the origin of Cometbid Social, and the plan for May and June as we build toward user accounts, authentication, and the social network launch.
Welcome to the Q2 2026 edition of the TCTF Roadmap Newsletter. April marked our first production release — v1.0.0 of the messaging and campaign platform. But before we look ahead, we want to share the story behind one of the biggest decisions we made this year: the pivot from a forum to a social network. That decision, made in February, reshaped everything you will see in the months ahead.
On April 8, we shipped v1.0.0 — the first production release of the TCTF platform. This release focused on the communication backbone that every future feature depends on.
What shipped: a multi-channel messaging platform with support for Email, SMS, WhatsApp, and Push notifications. A campaign management system for newsletters and community updates. Automatic failover across multiple email providers to ensure reliable delivery.
The platform infrastructure also went live — CI/CD pipelines with automated security scanning, end-to-end testing, and the deployment architecture that will carry us through to the October launch.
🚀v1.0.0 shipped April 8 — our first production release. The communication backbone is live: campaigns, newsletters, multi-channel delivery, and the infrastructure to scale what comes next.

Before we look at what is coming, it is worth understanding why we are building what we are building. The Cometbid Technology Foundation started with a vision for a global forum — a persistent, searchable space where the open-source community could discuss projects, architecture decisions, and roadmaps.
But in February 2026, we realized something important. A purely technical forum would alienate the people who are essential to open-source projects but do not write code — designers, project managers, technical writers, community builders, and users. The discussion culture in technical forums naturally gravitates toward code, pushing non-technical voices to the margins.
So we pivoted. Not away from the forum, but toward something bigger. We decided to build both: a forum at cometbid.org for focused, technical open-source discussions, and a professional social network at cometbid.com — Cometbid Social — where participation is not gated by technical depth. A designer can share a portfolio piece. A project manager can post a roadmap update. A student can ask for career advice.
The key insight was that both platforms could share the same backend. The social network service, the activity service, authentication, and messaging all serve both use cases. What differs is the frontend experience — cometbid.org presents content in a forum layout with threaded discussions, while cometbid.com presents content in a social feed with posts, profiles, and discovery. Features built for one platform benefit the other.
This dual-platform, shared-codebase approach shaped the entire 2026 roadmap. Every backend service we deploy serves both the forum and the social network. Every template we build works across both platforms. The investment compounds.
🔀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.
May is about preparing the experience users will see when they first arrive. Across our platforms, we are building user profiles, security settings, privacy controls, and messaging enhancements on Cometbid Social. The Member Dashboard gets document management with upload, preview, and download capabilities, plus a resume builder with PDF and DOCX export.
On the admin side, the Helpdesk Dashboard gets the tools the team needs to manage users — invitations, account activation, and security oversight.
May also brings file upload capabilities for avatars and documents, an achievement engine with leaderboards and rankings, and the admin backend that powers the Helpdesk Dashboard.
📋May focuses on the user-facing experience: profiles, document management, achievements, and the admin tools needed before onboarding begins.
June is the biggest deployment month of the year. This is when the platform gets its identity layer — the ability for users to create accounts, sign in securely, and manage their profiles.
User management goes live with member signup, email verification, profile management, invitations with accept/decline workflows, and the full account lifecycle. The authentication stack deploys in full — multi-factor authentication, sign-in with Google and GitHub, password management, session handling, and role-based access control.
The achievement system also launches with tier-based progression, leaderboards, and personalized recommendations — rewarding engagement from day one.
Performance improvements land alongside these features, giving each part of the platform its own optimized delivery pipeline.
Note: while the full signup and signin flow will be deployed and demo-ready in June, user onboarding will open later this year closer to the public launch.
⚡June brings authentication, user management, and the full signup/signin flow. The infrastructure will be live and demo-ready, with user onboarding opening later this year.
Q3 is when the platform becomes social. July brings the social network — profiles, connections, posts, reactions, comments, shares, and the activity feed. August adds billing and escrow, enabling paid projects with milestone-based payments. September ships project management — the place where teams find work, submit proposals, and collaborate on deliverables.
The public launch is targeted for October 2026. By then, the platform will support user accounts, social networking, billing, messaging, and project collaboration. AI features like translation and text generation will be present but launching post-release.
We will share the full Q3 roadmap in the July newsletter. For now, the focus is on May and June — building the foundation that everything else depends on.
🎯October 2026: Public launch with user accounts, social networking, billing, messaging, and project collaboration.
This newsletter is part of a 12-issue monthly series tracking our progress through 2026. Each month, we share what shipped, what is coming next, and behind-the-scenes stories from the engineering team.
Alongside the monthly newsletters, we publish a Framework Deep Dives series — starting in May with the DynamoDB single-table design patterns that power all 34 services. These technical articles go deep into the shared utilities and architecture decisions behind the platform.
Subscribe to make sure you do not miss an update. And if you are a developer interested in contributing, reach out — we are always looking for people who want to build something meaningful.

Q1 gave us the foundation — messaging, campaigns, and the infrastructure to deploy. Q2 is where the platform starts to take shape. By the end of June, the full authentication and user management stack will be deployed and demo-ready. The social network, billing, and project collaboration follow in Q3. We are on track for an October launch — stay tuned as we get closer.
Never miss an edition
Subscribe to get TCTF newsletters delivered to your inbox.