Change Layer Docs
    Checking session...

    Change Layer Docs

    Change Layer is a product management platform for developers and software teams. It helps teams manage products through changelogs, release notes, and roadmaps while making product context easier to use in modern development workflows.

    Start here

    If you are new to the product, read Getting Started first. If you are integrating with the current API surface, jump to the API section.

    What you can do with Change Layer

    • Create a team workspace for your company or product group
    • Add one or more products to that workspace
    • Publish product updates through changelogs and release notes
    • Organize longer-term product direction with roadmaps
    • Group individual changes under versioned releases
    • Share hosted product update pages with customers and internal teams
    • Use product data in app integrations, developer tooling, and automation

    Why teams use Change Layer

    • Keep product communication, planning, and release history in one place
    • Give engineering, product, and customer-facing teams shared context
    • Turn release activity into structured updates instead of scattered notes
    • Build toward AI-assisted and agent-driven workflows with better product context

    AI and agent workflows

    Change Layer is being shaped to support AI-native product workflows as part of its broader rebrand. That includes work on an MCP server and CLI so agents, scripts, and developer tools can use product context more directly.

    Where this is heading

    The goal is not just publishing updates. It is making product context accessible to developers, teams, and agents so shipping, documenting, and communicating changes becomes easier to automate.

    Core concepts

    • Team: the top-level workspace that contains members, products, settings, and billing.
    • Product: a single product or surface you manage. Products can have a changelog, release notes, and roadmap data.
    • Changelog: the public or internal page that groups versions for a product.
    • Version: a release entry such as 1.8.0 or Spring 2026.
    • Change: an individual improvement, fix, or announcement inside a version.

    Recommended reading path

    1. Read How Change Layer Works to understand the data model.
    2. Read Getting Started for the setup and publishing workflow.
    3. Read Team Roles if multiple people will manage updates together.
    4. Read API Authentication before building an integration.
    5. Read Get a Changelog and Get a Version for the current read patterns.

    Current API status

    The first public REST API routes are now available for published changelog reads. The broader authenticated API surface is still being built out, but public integrations can already use the new /v1/public/... endpoints for changelog and version fetches.

    Important to know

    Public reads are available for published data. Private workspaces and draft content stay behind authentication and membership checks.