Tooling

Climakers currently exposes two active commercial product groups and three live tools across them.

The tools share a common operator model, but they are optimized for different platforms and scopes of work.

All tools put the customer in control: they turn platform-bound data into customer-owned files, use local machine-bound license storage, and apply explicit operational boundaries — read-only where the job is export, and plan-first confirmation where a command can change remote state.

Active product groups

Atlassian Confluence

The first live product family. It contains the public manuals for acp2md and acs2md. Both tools are read-only and target Atlassian Confluence Cloud.

Atlassian Jira

The Jira Automation product family. It contains the public manual for ajat, which governs, backs up, reports on, compares, restores, and safely operates Jira Cloud Automation rules.

• Compare plans for every tool at store.climakers.com

acp2md

acp2md is the page-level specialist.

Use it when you need exact scope and exact control.

Commercial packaging: Hobbyist for individual operators and Multiple Seats for small teams that need the same focused page workflow on more than one machine.

• Convert one Confluence page by ID, title, or URL.
• Retrieve native atlas_doc_format or storage output without conversion.
• Count nodes and marks before migration or AI ingestion.
• Inspect page properties and preserve one authoritative document outside Confluence.
• Discover the right page safely with space list, space pages, and tree --short before exporting.

Best fit:

• legal and compliance evidence capture
• support and incident workflows
• migration engineering for difficult pages
• curated RAG source documents
• runbook and procedure retention

acs2md

acs2md is the space-scale export tool.

Use it when the requirement is an estate, not a single document.

Commercial packaging: Professional, Small Team, CI/CD Automation, Enterprise, Enterprise Pro, and Enterprise Plus for governed space-scale documentation programs.

• Convert a full Confluence space into a Markdown directory tree.
• Preserve hierarchy and rewrite internal links for portable output.
• Keep recurring exports efficient with changed-only sync behavior.
• Inspect spaces, pages, properties, and permissions from the same binary.
• Track long-running exports and native downloads with progress output on stderr.

Best fit:

• documentation continuity copies
• backup and disaster recovery archives
• static-site or Git migrations
• large AI and enterprise-search corpora
• governance and access-review workflows

ajat

ajat is the Jira Automation governance tool.

Use it when the requirement is to own, audit, and safely operate a Jira Cloud automation estate rather than convert Confluence content.

Commercial packaging: Trial, Solo, Team, CI/CD Automation, and Enterprise for teams managing automation across many projects and tenants.

• Export every Jira Cloud Automation rule to a scope-aware JSON tree.
• Generate five self-contained HTML reports: inventory, collision, consistency, risk, and workflow.
• Compare two export snapshots locally to review drift, with a CI --check gate.
• Search live rule summaries through the Automation API.
• Operate rules in bulk (enable, disable, delete, rescope) and restore or promote rules through explicit import plans — all plan-first with --dry-run and --yes.

Best fit:

• automation inventory and governance reviews
• backup, retention, and disaster recovery for rules
• data-egress and integration audits
• sandbox-to-production promotion
• incident pause-and-recover and CI drift gates

Shared operating model

All tools are designed around the same core workflow:

1. activate the license
2. configure platform access — Confluence for acp2md and acs2md, Jira for ajat
3. run doctor
4. discover the correct scope — space list and space pages for the Confluence tools, search and export for ajat
5. execute the export, report, or operation command

Shared platform characteristics

• customer-controlled output files — Markdown or native payloads for the Confluence tools, JSON exports and self-contained HTML reports for ajat
• Atlassian API-token authentication (Confluence Cloud or Jira Cloud)
• commercial licensing and local, machine-bound license storage
• CLI-first execution suitable for local operations, CI, and governed automation
• explicit safety boundaries: read-only export commands, plus plan-first --dry-run / --yes confirmation for any command that changes remote state (ajat import, rule, and invoke)
• discovery and readiness commands such as doctor and tree
• released builds for macOS and Linux across all tools (Linux on both amd64 and arm64); there is no Windows build

Support

When operators hit installation problems, licensing issues, configuration errors, connectivity failures, or unexpected command behavior, use the Climakers support workflow instead of guessing from incomplete evidence.

• Contact support@climakers.com for product errors, operational incidents, and workflow questions.
• Include the product name, version, platform, sanitized command, and the exact observed error.
• Never send credentials, API tokens, license keys, session cookies, or confidential customer content.
• Expect a response as soon as possible; clearer reproduction details usually reduce turnaround time.

Use the full Support page for the complete support process, safe disclosure guidance, and a support email template.

Reserved future product groups

Google Workspace

Reserved for future Google Workspace-oriented tooling and workflows.