Chainlog already supports the core workflow from source capture to trusted publishing. Features that are not ready for broad release are called out as coming soon.
These capabilities are implemented in the current product surface and should be safe to market as available.
Generate draft updates from synced engineering artifacts, then review, edit, approve, and publish from one workflow.
Connect source systems, browse scoped objects, and sync technical artifacts into Chainlog for operator review.
Control visibility and let readers filter updates by audience, platform, delivery type, release status, and custom taxonomy.
Support subscribe, confirm, unsubscribe, and publish-time email notifications for relevant releases.
Publish on the web and expose RSS, Atom, and JSON feeds for customers, internal teams, and external tooling.
Create entries programmatically, manage API keys, and notify downstream systems on publish, update, archive, and delete events.
Queue launches for later and automate recurring BAU, monthly, or quarterly update cadences.
Track views and interactions, filter dashboard reporting, and export data as CSV or XLSX.
Keep operational history, export Ghost Mode access records, and cryptographically sign published entries.
These capabilities are visible in the codebase or product direction, but they are not ready to position as broadly available yet.
Custom-domain support is partially wired today, but seamless onboarding and provisioning are still coming soon.
Widget credentials and runtime exist, but a more polished embedded product surface is coming soon.
The platform already supports generic webhooks. Native downstream destinations are coming soon.
Subscriber preferences already anticipate more channels, with in-app delivery coming soon.
Ready to put a proper release communication system in front of customers?