02Quickstart

Install, configure, and verify your first workflow.

Seven concrete steps for the downloadable application. Timing depends on your operating system, identity provider, connector permissions, and deployment scope.

Use a non-production environment first

This checklist does not authorize production changes. Use dedicated test accounts and least-privilege credentials. The website sandbox is isolated sample data; the installed app must display actual connection and operation results.
  1. 01

    Download the correct installer

    release-backed

    Use the live release manifest to choose the build matching your operating system and architecture. Review the displayed signing or notarization status before installing.

    Download Axiom Agent
  2. 02

    Install and launch Axiom Agent

    platform-specific

    Follow the platform instructions. Do not bypass an unsigned-software warning where your organization forbids unsigned applications.

    Installation guide
  3. 03

    Complete desktop authentication

    identity required

    Start sign-in from the installed app. Approve the short-lived pairing request in your browser, then return to Axiom Agent. The browser flow authenticates the desktop; it is not a hosted product.

  4. 04

    Confirm the empty workspace

    no sample fallback

    Before adding data, verify that catalogs, requests, approvals, evidence, and integrations show explicit empty or disconnected states instead of fictional records.

  5. 05

    Configure one safe integration

    connector-dependent

    Install the GitHub App on a dedicated test repository first. For AWS ECS, configure a non-production environment target and a narrowly trusted GitHub Actions OIDC role.

    AWS setup guide
  6. 06

    Create and review a deployment request

    approval-gated

    Capture intake, resolve readiness checks, choose the versioned playbook, and collect the required approvals. Missing permissions or rejected approvals must block progression.

    Approval workflow
  7. 07

    Validate, collect evidence, and close

    human-confirmed

    Use only the configured tenant workflow, record the observed ECS validation result, preserve the action evidence, and confirm the rollback path before enabling production.

    AWS ECS rollback

Completion evidence

  • ✓ Installed version and architecture recorded.
  • ✓ Desktop pairing approved and session state visible.
  • ✓ Connector result reflects the real configured service.
  • ✓ Request, approval, validation, evidence, and closure states persisted.
  • ✓ Any blocked or unavailable capability remains explicitly labeled.

Read next

Security model

Access, storage, tenant boundaries, and revocation.

Best practices

Readiness, approval, validation, and operational safeguards.

AWS ECS setup

Configure the tenant workflow, OIDC role, and deployment target.

Desktop installation

Platform requirements, signing status, first launch, and updates.

Still blocked?

Include the failed step and error. Never send a password, token, or cloud secret.

Open support request