Questions, answered plainly.

LaunchPad structures Jira Assets so reporting, automation and Rovo agents have something real to work with.

Instead of spending months designing CMDBs, ownership models and operational structures from scratch, it installs structured Assets patterns that teams can start using immediately.

• IT and service-management teams
• Jira administrators
• CMDB and asset managers
• Enterprise organisations
• Atlassian partners and consultants
• Teams migrating from ServiceNow

LaunchPad deploys structured patterns into Jira Assets, including:

• Object types
• Attributes
• Relationships
• Ownership structures
• Service-mapping foundations
• Governance-ready operating models

The catalogue currently spans 13 schemas, covering areas such as CMDB, Enterprise IT, Software Asset Management, Cybersecurity, Service Catalogue and Workforce Management. Environment Analysis and the Excel workbook import work across the whole catalogue, and across schemas you already have.

No. Templates are usually static examples.

LaunchPad deploys operationally structured models designed for real service environments, with relationships, ownership logic and governance foundations built in.

Most Jira implementations focus on workflows. LaunchPad focuses on operating structure.

The goal is moving organisations from unclear ownership, inconsistent data and manual routing to structured operating models, clear accountability and reporting that scales.

Most organisations can begin deploying service structures within minutes.

Time to full operational maturity depends on your existing Jira setup, governance requirements, organisational complexity and existing CMDB quality.

Yes, alongside it.

Deployments are additive: every schema LaunchPad installs sits next to your existing Assets schemas without modifying them. You can run both, route between them, and migrate at your own pace.

You do not need to start from scratch, and nothing you already have gets merged or rewritten to make room for a new schema.

No.

LaunchPad follows a review-first, additive deployment approach. Existing data and configurations are never overwritten, and you stay in control of what gets deployed into your environment.

Yes. Everything LaunchPad deploys remains fully editable within Jira Assets.

Add attributes, extend object types, modify relationships and adapt models to your internal processes.

No.

LaunchPad is designed to reduce the complexity of building structured service models in Jira Assets, giving teams a strong operational starting point without architecting everything manually.

Yes, as an on-ramp. It gives you a structured place to land: a model to map into, an Excel workbook to populate with your exported data, and structured fields ready to connect to your requests.

There is no connector. You control the export and the mapping, and LaunchPad validates every value you bring against the schema before it imports.

Yes. LaunchPad is built entirely on Atlassian Forge:

• No external servers
• No customer data leaves Atlassian Cloud through LaunchPad
• No API-token collection
• Native Atlassian authentication and permissions

A full CSA CAIQ v4.1 self-assessment is published on our security page: 283 controls across 17 security domains, covering LaunchPad and Second Chance. It is a direct download, no request needed.

• LaunchPad overview
• Documentation
• Security information