Firestartr
EnglishEspañol
Search Firestartr
The platform that makes your organization explicit

Your IDP tailored to your needs

Firestartr is an open-source framework for building internal developer platforms. It connects domains, systems, components, teams and infrastructure so your platform can create, deploy and evolve software with clear rules.

Read the documentationView on GitHub
firestartr
commercedomain
checkout-systemsystem
paymentscomponent
checkout-teamowns checkout-system
one modelmany consistent outcomes
One model for development, platform and infrastructure
When software grows

Organizations lose the map before they lose control

Firestartr starts by making your software visible. Then it turns that knowledge into repeatable, reviewable automation.

01

Every repository invents its own way of working.

Different CI/CD, release and configuration patterns for problems that should be solved once. Each team ends up maintaining its own solutions, and shared improvements take longer to reach everyone.

02

Architecture stops having recognizable boundaries.

Systems and dependencies exist, but nobody shares a clear view of how they fit together. Without that map, understanding the impact of a change or who it affects means rebuilding the context every time.

03

Responsibility becomes diffuse.

When ownership, permissions and infrastructure live apart, operating becomes slow and risky. Decisions get stuck, and resolving an incident can start with figuring out who should act.

The model

From business domains to deployed software

Firestartr organizes software around the same boundaries the business recognizes. Each level gives context to the next.

commercedomain
inventory-systemsystem
catalogcomponent
checkout-systemsystem
paymentscomponent
Owner: checkout-team
An e-commerce platform
Domains

Group the systems serving one part of the business.

Systems

Define functional boundaries with clear responsibility.

Components

Connect a software unit to its repository.

Teams

Make ownership of every component visible.

Features

Add reusable capabilities to a repository.

Infrastructure

Keep supporting resources beside the software using them.

Three surfaces, one model

Work where your team already works

Review changes in GitHub, explore and provision through Firestartr Portal, or request operations in plain language with Firestartr skills.

GitHubCode and change reviews

Repositories, pull requests and workflows apply approved changes.

Firestartr Portal (Backstage)Catalog and self-service

Browse components, find ownership and manage resources through guided flows.

Firestartr skillsConversational operations

Describe what you need; an agent interprets the context and prepares the right operation.

GitHub, Firestartr Portal and Firestartr skills as work surfaces
Agents with guardrails

Let your agents move fast. Firestartr keeps the rules in place.

Give your agents room to work while keeping each change grounded in how your organization is structured.

Agents at work, with guardrailsCONTROLLED FLOW
Any agentChoose the agent your team prefers
Skill: firestartr-operationFor working with FirestartrRepos · Teams · Users · Systems · Domains
Command: fs-forge-cliUsed by firestartr-operation
GitHub pull requestsChanges ready for review
Cloud deploymentsOn your cloud provider

Context and rules turn a request into an operation

Prefapp ready-to-use skills

From a request to a repository ready to use

See how a Prefapp skill asks for missing details, prepares a plan and opens a pull request to create a repository with release_please.

From intent to change

Automation you can review

Each stage makes clear what was requested, which rules were checked and where your team reviews the outcome before it is applied.

  1. 01
    Instruction

    Describe the change your team needs.

  2. 02
    Firestartr

    Place the change in your organization’s context.

  3. 03
    Policy validation

    Check permissions and rules before proposing changes.

  4. 04
    Human checkpointPull request

    Your team reviews and approves before applying.

  5. 05
    Provisioned resource

    The approved state reaches your platform.

Reusable Features

Compose each component with the capabilities it needs

Choose Features—reusable capabilities—from the catalog and compose them into each component. Their files, workflows and configuration are ready to integrate, review and evolve without starting from scratch.

  • Builds and releases
  • Templates and documentation
  • Infrastructure as code
  • Workflows and configuration