Your assets. In Jira.

AssetPilot brings inventory, ownership and asset lifecycles into Jira. Give every request the context it needs.

Explore apps

Built on Atlassian Forge.
A product by Plugins Factory.

AssetPilot ConnectYour device tools, connected to Jira

AssetPilot for Jira

Your inventory, with the whole story.

Open product tour

AssetPilot inventory preview with asset tags, device names, statuses, assignees and locations

Product previews with sample dataSee the workflow

Know every asset.

One register for your devices, owners, locations and history. Open the same record from the Jira issue that needs it.

Asset inventory

Find equipment by tag, serial number, owner or location. Select several assets to update their status or move them together.

From arrival
to return.

AssetPilot CSV import preview with column mapping and validation

Bring your inventory

Map your CSV columns, review row errors and choose how to handle matching asset tags or serial numbers before you import.

Assets linked to a Jira request, with check in and check out actions

Put it to work

Link equipment to a request. See the reporter’s assets. Check devices in or out without losing the ticket’s context.

Asset record with assignment, warranty, QR code and timestamped activity

Keep the asset history

Track assignments, returns, warranties and changes. Give every device a record your next teammate can understand.

Built for the work
around the asset.

Reservations & due dates
Repair & maintenance logs
QR labels & custody checks
Custom asset types & fields
Kits & offboarding
Depreciation & stock levels

Keep your tools
in sync.

AssetPilot Connect brings device data from Intune, Jamf Pro and Kandji into your register, then sends asset updates where your team works.

A separate, optional app. Free with AssetPilot.

Microsoft IntuneJamf ProKandji

AssetPilot ConnectPreview · Sync · Review

AssetPilotSlack & TeamsWebhooks & API

How data moves through your connected workflow

Preview before you sync

See the impact before writing to your register. Choose hourly, six hourly or daily updates, with a record of created, updated and skipped devices.

Keep ownership intact

Preserve existing assignments when device data refreshes. Decide whether names may be overwritten and available devices assigned.

Make events actionable

Choose which changes reach Slack or Teams. Use signed webhooks with delivery history, or scoped, revocable API keys for your own tools.

The device. The owner.
The ticket. Together.

Plugins Factory builds for the moment an IT team needs an answer. The inventory and the request belong in the same workflow.

Know where
your data goes.

Start your security review with the actual architecture: a Forge core for your inventory and a separate companion for external connections.

Atlassian Forge

AssetPilot

Asset register
Ownership & history
Jira issue context

Atlassian hosted storage

Optional installation

AssetPilot Connect

Connections to services you configure

A defined storage boundary: AssetPilot stores core asset data in Atlassian Forge. Its core manifest has no external fetch permissions.
Access through Jira groups: Assign admin, manager and viewer roles through Jira groups so the people managing equipment have the access they need.
A record of what changed: Per asset history and a global audit log make assignments and updates visible to your team.
Deliberate external connections: Connect handles configured MDM services and outbound notifications separately. Review its scopes and destinations for your organization.

Before you install.

ProductsDo I need both apps?

No. AssetPilot works as your core asset register. Install AssetPilot Connect only when you need MDM synchronization, external notifications, webhooks or an API gateway.

MigrationCan we start with a spreadsheet?

Yes. Import a CSV, map its columns to asset fields and review validation results before committing. Matching asset tags or serial numbers can be skipped or updated.

DeploymentWhich Jira platform is supported?

These apps are built on Atlassian Forge for Jira Cloud. The product architecture shown here is not a Jira Data Center deployment.

IntegrationsWill a sync replace our assignments?

Existing assignments are preserved. Connect lets you choose name overwrite behavior and whether available devices can be assigned. Preview a sync and review its results before enabling your preferred schedule.

EvaluationWhat should procurement review?

Confirm the current installation link, licensing and trial terms, requested permissions, data flows, retention, privacy terms and support commitments. The evaluation brief below brings these questions into one document.

CompanyIs Plugins Factory part of Atlassian?

Plugins Factory is an independent company building apps for the Atlassian ecosystem. Jira and Atlassian are trademarks of Atlassian.

Plan your rollout.

Turn your requirements into a brief for your IT, security and procurement teams.