Our Extensions

Extensions for
Azure DevOps & Atlassian

Every one of them runs entirely inside the platform it extends — native identity, no external backend, and none of your content leaving your tenant. They cover different surfaces, so most teams run whichever ones match their stack.

Which one do I need?

Governing your Wiki

You need approvals, owners, and an audit trail on Azure DevOps Wiki pages.

Governance for Wiki →
Diagramming your work

You need draw.io diagrams in work items, repository files, and pull requests.

Contextra Draw →
Writing in Arabic

Your Confluence Cloud pages are in Arabic or another right-to-left language and read in the wrong order.

RTL Pro →
Controlling file uploads

You need rules on file type, size and count for attachments on Jira issues or JSM requests.

File Field →
Protecting a secret value

You need a password or API-key field on a Jira issue that stays encrypted and hidden from anyone not explicitly allowed to see it.

Secure Field →

All products

Flagship

Governance for Wiki

Azure DevOps Wiki

Approve, track, and audit Azure DevOps Wiki changes without leaving your Wiki.

Turns your existing Wiki into a governed, audit-ready documentation platform. Draft → In Review → Approved lifecycle, immutable audit log, ownership and SLA tracking — no migration, no external systems.

  • Draft → In Review → Approved approval workflow
  • Immutable, append-only audit trail
  • Page ownership, reviewers & SLA tracking
  • Rich-text editor with draw.io diagrams inside Wiki pages
  • Compliance dashboard for ISO 27001 / SOC 2 evidence
Explore Governance Pricing
View on Azure DevOps Marketplace ↗
New

Contextra Draw

Work Items · Repo Files · Pull Requests

draw.io inside Azure DevOps Work Items, repositories, and pull requests.

Embed and edit diagrams everywhere your team already works — without leaving the platform, and without your diagrams ever leaving your Azure DevOps boundary.

  • Full draw.io editor embedded in the work item form
  • Diagram repository files and pull requests
  • Offline templates — flowcharts, architecture, org charts
  • Complete version history for every diagram
  • Works with Azure DevOps Services and Server
Explore Contextra Draw Pricing
View on Azure DevOps Marketplace ↗
New

RTL Pro for Confluence

Atlassian Confluence Cloud

Arabic and right-to-left text that reads in the correct order.

Confluence has no concept of text direction, so an Arabic sentence containing an English word comes out with its phrases reversed — and the align-right button does not fix it. RTL Pro fixes reading order in pages, titles and comments, and moves list markers to the right.

  • Fixes reading order, which alignment alone cannot do
  • Moves bullet and number markers to the right
  • Page titles and comments fixed alongside the body
  • Scan and fix an entire space, or fix automatically on save
  • One-click undo — every change is an ordinary page version
Explore RTL Pro Limitations
View on Atlassian Marketplace ↗
New

File Field for Jira

Jira Cloud · Jira Service Management

Dedicated attachment fields with rules — separate from the built-in attachment box.

Jira's built-in attachment box takes any file, of any size, with no rules and no way to require one before a request moves on. File Field adds dedicated custom fields with type, size and count limits, and your choice of Portable (real Jira attachments) or Private (permission-restricted) storage, per field.

  • Restrict by file type, category or MIME, and cap size and count
  • Catches a renamed file — content checked against its extension server-side
  • Portable (real Jira attachments) or Private (permission-restricted) storage, per field
  • Test your rules before anyone hits them, without uploading anything
  • Works on issues and on JSM portal request forms
Explore File Field Limitations
View on Atlassian Marketplace ↗
New

Secure Field for Jira

Jira Cloud · Jira Service Management

A password/API-key field that stays encrypted and hidden from everyone but an explicit allow-list.

An ordinary Jira custom field puts its value in plain text, readable by anyone with issue-view permission through Jira's own REST API — exports, JQL and integrations included. Secure Field encrypts the value server-side and gates every reveal against a per-field allow-list, re-checked on every request, with a full audit trail of who saw what and when.

  • AES-256-GCM encryption; the raw value never touches the field's own Jira-visible schema
  • Deny-by-default reveal, by user, group, role, assignee, reporter, creator or project lead
  • Immutable audit log of every reveal, edit, and denied attempt
  • Optional second-factor confirmation and auto-expiry (TTL) per field
  • Two-phase migration wizard to encrypt an existing plain field's values, admin-confirmed before the original is cleared
Explore Secure Field Limitations
View on Atlassian Marketplace ↗
Common to All

Built to Clear
Your Security Review

Native Identity

No separate login and no custom RBAC model — each app uses the host platform’s own identity.

No External Backend

Nothing is processed on servers we operate.

No External Storage

Your content stays inside your Azure DevOps or Atlassian tenant.

Minutes to Install

Install from the Marketplace. No migration required.

All start with a 30-day free trial

No credit card required. Install from the Azure DevOps or Atlassian Marketplace and evaluate on your own projects.

Governance Pricing Contextra Draw Pricing RTL Pro File Field Secure Field