Skip to main content
addly

An Atlassian app should never require a leap of faith.

addly designs Jira and Confluence add-ons that teams can understand, see, verify, and prepare to deploy before the concepts reach their future Marketplace listings.

Explore the apps View a guided demonstration

Design showcase: products, data, and statuses are explicitly fictional until they are connected to a real Marketplace listing.

Evaluation record

Evidence follows the buying journey

  1. 1ProblemUse case and role identified
  2. 2ProductDemonstration in host context
  3. 3TrustPermissions and data made explicit
  4. 4RolloutDocumentation, app-data migration, and support
  5. 5MarketplaceOfficial link after publication

Every doubt has its own page.

01Understand
02See
03Verify
04Deploy
05Adopt

Four products. Four places where work needs a clearer view.

The catalog does not begin with a feature list. It shows the exact moment in Jira or Confluence where each app becomes useful.

P–01Readiness for JiraJira · Issue panelDecide whether a release is ready without leaving the issue.Evaluate the app P–02Portfolio InsightsJira · Project pageRead risks, decisions, and dependencies at project level.Evaluate the app P–03Page SummaryConfluence · Content macroTurn a dense page into readable decisions and actions.Evaluate the app P–04Context LinkerConfluence · Context panelFind related projects and decisions without leaving the page.Evaluate the app

The demonstration is not a decorative video.

It places the product in the flow, reveals its states, and tells evaluators exactly what to observe before deciding.

Choose a guided scenario

addly Readiness

Pre-release check

IN REVIEW
67%

2 of 3 criteria are ready

Demonstration data · Controls rendered with official Atlaskit components.

Read the verdict, then trace it back to its cause.
addly · SMART SUMMARY

What to take away

The committee approved the new journey. Three actions remain open before the June 24 pilot launch.

CURRENT
DECISION

Pilot journey approved

FOLLOW UP

Finalize the adoption measure

Demonstration data · Controls rendered with official Atlaskit components.

Context stays attached to the evidence.

A useful summary preserves its sources, limitations, and next action. The product page then explains permissions, data, and compatibility.

Inspect Page Summary

Five questions. One decision journey.

The evaluation journey is reorganized around the buyer: each destination resolves a doubt and points to the next.

  1. 01Is this my problem?Scenarios by role and moment provide context before features.Choose a use case
  2. 02What does the app look like?Every product can be manipulated in a credible Jira or Confluence surface.Start a demonstration
  3. 03Can I trust it?Permissions, data, limitations, and expected evidence remain accessible before installation.Assemble the record
  4. 04How do I deploy it?Documentation, migration, compatibility, and support prepare the app’s own configuration and rollout.Prepare deployment
  5. 05What happens next?The changelog, status, and roadmap make the product lifecycle visible after purchase.Track the product

Trust does not arrive at the bottom of the page.

The evaluation record is deliberately more honest than a wall of badges. It separates what is described, what still needs validation, and what does not exist yet.

Open the Trust Center View the documentation
T–01Evaluation recordMarkdown export per appT–02PermissionsDescribed per appT–03DataFlows and limitations visibleT–04SubprocessorsCurrent local state separated from future plansT–05ComplianceNo invented evidenceT–06SupportDiagnostic prepared

S–00

The rare good ideas become a system.

S–01Exportable recordEvery app produces a Markdown packet of evidence, blockers, and the decision.Open S–02Honest comparisonsNative features, an app, and a manual process are compared with their limitations.Open S–03Transparent calculatorAssumptions are editable and the formula remains visible.Open S–04Roadmap without false promisesEvery horizon states its level of commitment.Open S–05Genuinely useful templatesEvaluation, security, and app-data migration become copyable templates.Open S–06Known limitationsEvery concept publishes its limitations and the intended workaround format.Open

F–01

Start with the app. Finish with a record you can defend.

Choose a product, interact with its demonstration, then review documentation, trust, pricing, and adoption in the same order as your decision.

Choose an app Assemble the record