Guides

The guides take one task from start to finish and tell you which fremforge feature to use at each step. They are written to be read in order. The other sections of this documentation are the reference: one page per feature, with every setting, scope and endpoint. Each guide links to the reference pages it uses, so you can go deeper wherever you need to.

The guides

• Your first hour with fremforge, for the person who becomes the organisation’s first owner: signup, email verification, first login, SSO, payment, break-glass preparation and inviting teammates.
• Migration guides, moving to fremforge from another platform:
  • Pre-migration checklist, a read-only scan of your current tenant to find blockers before you start.
  • From GitHub, from GitLab and from Azure DevOps, step by step.
  • Alongside GitHub, scanning your repositories on fremforge while code and CI still live on GitHub.
  • Secrets in history, importing a repository whose old commits contain secrets.
• Working with AI agents on fremforge, for teams that run coding agents: fremforge’s AI posture, a scoped credential per agent, declaring work before it starts, the event feed, merge holds, asking why a pull request has not merged, release trains, risk tiers and the MCP server.

Not sure where to start?

If you are setting up fremforge for your organisation, start with your first hour. If you are a developer pushing code for the first time, Getting started is the shorter path. If your code lives somewhere else today, run the pre-migration checklist first.