Basic CMDB
Servers and applications mapped to people. The minimum viable CMDB structure for service accountability.
Deploy a working service structure in minutes.
LaunchPad installs a service operating model inside Jira Service Management so tickets route, ownership exists, and reporting works from day one.
- Platform
- Atlassian Forge
- Compatible
- Jira Service Management (Cloud)
- Data
- Never leaves your tenant
- Models
- 13 production-ready
What LaunchPad does
Four capabilities, one install.
Everything the app does is in service of one outcome: a working service model inside your JSM instance, from day one.
// 01
Service model deployment
A pre-built Assets schema is installed into your instance. Object types, attributes, relationships, icons — all ready.
- Object types created
- Attributes configured
- Relationships mapped
- Ownership structure in place
// 02
Environment analysis
Your Jira instance is scanned to surface what already exists. Projects, service desks, request types, custom fields. Recommendations are generated from real usage, not assumptions.
- Full instance scan
- Service model recommendation
- Gap and overlap surfacing
// 03
Request flow integration
Request types connect to deployed Assets fields so tickets carry the context they need from the moment they're raised. No manual linkage, no drift.
- Request-to-asset mapping
- Structured field population
- Routing by service ownership
// 04
Safe, additive deployment
Nothing is overwritten. Existing schemas, existing data, existing configuration — all untouched. Every deployment sits alongside what's already there.
- Additive only
- Zero modification of existing data
- Clean rollback available
What LaunchPad does not do
The things we deliberately left out.
This is a product, not a programme. The boundary matters — both for what you're buying and for how fast you can start.
No workshops or onboarding
The app installs structure directly. No kickoff calls, no discovery sessions, no implementation programme.
No process redesign
LaunchPad deploys structure, not methodology. How your teams work is your decision.
No custom implementations
Customisation is handled through Schema Extensions — as importable structures, not consultancy engagements.
No replacement of Jira or JSM
LaunchPad runs inside your existing Atlassian tenant. Nothing moves, nothing migrates.
LaunchPad does not configure Jira. It installs the structure Jira needs to work properly.
What gets installed
The result is a connected model in Assets.
Service
Payroll Service
Owner: Finance Ops
Application
ADP Workforce
Vendor: ADP
Team
Finance Ops
12 members
Server
adp-prod-01
AWS eu-west-2
Database
adp-payroll-db
Postgres 15
Request type
Payroll issue
Routed to Finance Ops
runs_on→owned_by→depends_on→supports→references→
After a Standard CMDB deployment, your Assets workspace holds a connected model that mirrors how your service desk actually operates.
- Object types appear in AssetsServices, applications, infrastructure, teams, and request types — all visible in the Assets UI.
- Relationships connect themServices run on applications, applications run on infrastructure, infrastructure belongs to teams.
- Ownership is explicitEvery service has a named team. Every team has a route. Every route carries context.
- Request types reference itNew tickets arrive with the right context attached. No triage, no missing fields.
Service model library
Thirteen models across four tiers.
Each tier targets a different stage of JSM maturity. Start where you are — move up when the model you've got is no longer enough.
StarterMinimum viable structure
1 modelOperationalWhere most JSM deployments land
5 modelsCore Schema
People, teams, applications, and vendors with ownership mapped across your organisation.
Standard CMDB
Servers, databases, applications, and network devices with ownership, location, and dependency mapping.
Service Catalogue
Service categories, SLAs, support teams, and knowledge articles mapped to business services.
Priority Matrix
Impact and urgency mapped to priority levels with clear escalation paths.
SLA Management
SLA policies, escalation rules, and tracking structures mapped to services and support tiers.
AdvancedSpecialised domains
3 modelsCloud-Native Infrastructure
Kubernetes clusters, containers, serverless functions, and managed services with clear team ownership.
Cybersecurity Asset Inventory
Security assets, vulnerabilities, controls, and compliance requirements with clear ownership.
Software Asset Management
Licences, entitlements, installations, and compliance positions tracked per publisher. Audit-ready from deployment.
EnterpriseFull-estate structure
4 modelsEnterprise IT CMDB
Infrastructure, applications, services, compliance, and multi-cloud operations unified in a single schema.
Vendor Management
Vendors, contracts, risk assessments, and performance tracked against SLAs.
Workforce Management
Employees, contractors, skills, certifications, and equipment tracked with department ownership.
Documentation Management
Page ownership, review cadences, validation status, and capability claims tracked with release readiness.
How it fits your stack
Native to Atlassian. Nothing else required.
Platform
Atlassian Forge
Runs inside your Atlassian tenant. No external hosting, no intermediary services, no vendor lock-in beyond Atlassian itself.
Product
Jira Service Management
Deploys into your existing JSM instance. Compatible with Assets as shipped. No modifications to Jira or JSM required.
Data
Your tenant, your data
Nothing leaves your site. No external database, no analytics phone-home, no vendor-side storage of your configuration.
When the core models aren't enough.
Schema Extensions customise what LaunchPad already deployed — purpose-built importable structures for use cases that sit outside the standard library. One-off deliverables, not consultancy.
See pricing and availabilityPost-launch
Specialised extensions
On request
Custom extension work
Designed as
Reusable products
Delivered as
Importable structures
Playbooks · Q3 2026
Structured operational guidance for teams scaling beyond initial deployment. A separate offering — not required to use LaunchPad.
Learn more
Install LaunchPad. Deploy in minutes.
No workshops. No onboarding. No calls.