Runs on Atlassian Ready Zero External Egress Marketplace Vendor #400414966

Enterprise Confluence & Compliance Software Built for Zero-Trust Teams

ClearStack Works engineers self-contained Atlassian Forge apps and corporate compliance utilities. Designed for IT administrators, InfoSec reviewers, and engineering leaders who refuse proprietary macro lock-in or external data exfiltration.

0 External Domains No external backend, analytics, or telemetry declared in manifest.yml.
100% Native ADF Pages stay natively editable even if the plugin is uninstalled.
< 24h Business SLA Direct engineering support with global business-day SLA coverage.
Paid via Atlassian Standard Marketplace EULA, corporate card, and PO invoicing.
Flagship Atlassian Forge App Zero Macro Lock-in Bidirectional Sync

Markdown Tree Sync — Bulk Import & Export (Native Pages)

Keep Confluence Cloud synchronized with Git repositories, Obsidian vaults, and AI RAG documentation pipelines without fragile macros or company-wide GitHub OAuth permissions.

Enterprise InfoSec & Architecture Comparison for Confluence Markdown Sync
Evaluation Criteria ClearStack Works (Forge ADF) Legacy Macro Importers Git OAuth Connectors
Confluence Storage Format 100% Native Confluence Cloud ADF pages & native attachments Wraps content in proprietary closed Markdown macros Dynamic remote macro embed (not native Wiki pages)
Uninstall Safety All pages & images remain 100% intact and editable forever Pages break or render raw unformatted syntax after uninstall Rendered repository views disappear after uninstall
External Network Egress Zero external egress (runs strictly inside Atlassian Forge) Often routes conversion through vendor-hosted servers Streams repository files via external SaaS relays
GitHub OAuth Requirement None required — drag & drop local folders or .zip archives Usually flat single-file or broken folder import Requires org-wide GitHub OAuth read tokens (often blocked by InfoSec)
Local Images & Internal Links Two-pass upload binds local ./assets/ attachments & rewrites cross-links; offline-ready export Relative image paths & nested README.md trees frequently fail Remote image URLs break in offline Git/Cursor/RAG exports

Core Enterprise Capabilities of Markdown Tree Sync

Built exclusively for Confluence Cloud engineering workflows — nested folder & subtree imports, idempotent team sync, and clean offline exports.

Idempotent Team Sync Conflict Guard

Safe Dry-Run & Conflict Guard

Sub-second structural preview under your chosen parent page with title collision resolution, preserving Confluence comments, version history, and online colleague edits.

Zero-Pollution Export Offline Assets

Clean Git, Obsidian & AI Context ZIP

Position-aware subtree export with offline ./assets/ image binaries and clean unpolluted filenames ready for Git repositories and RAG pipelines.

Enterprise Procurement & InfoSec Due-Diligence FAQ

Does ClearStack Works transmit or store our Confluence pages on external servers?

No. Our Atlassian Forge apps declare zero external egress domains in manifest.yml. ZIP extraction, AST transformations, and rate-limited page API calls run locally inside your browser Custom UI sandbox (with stateless, ephemeral attachment relays strictly inside Atlassian-hosted Forge functions) and communicate exclusively with your Confluence Cloud tenant via Atlassian's official @forge/bridge and @forge/api.

What happens to imported pages if our organization uninstalls the app later?

Every imported document is saved as a 100% standard Confluence Cloud native page (atlas_doc_format) with standard Confluence page attachments. Nothing is locked inside proprietary macros, so your Wiki stays cleanly formatted and editable permanently.

Why do you support local .zip and folder upload instead of requiring GitHub OAuth?

Many enterprise InfoSec teams block third-party Marketplace apps that demand broad GitHub or Bitbucket OAuth repository access. Local folder selection, multi-file drops, or .zip import lets engineering teams publish documentation subtrees or entire repositories interactively behind strict corporate firewalls with zero OAuth exposure.

How are licensing, evaluation trials, and enterprise invoices handled?

All commercial Confluence apps are distributed via Paid via Atlassian under the official Atlassian Marketplace Standard EULA. Atlassian handles 30-day evaluations, per-site billing, corporate credit cards, and enterprise Purchase Orders directly.

Are your standalone web SaaS products isolated from your Atlassian Forge apps?

Yes. positivepayfilegenerator.com and foodnutritionlabelmaker.com run on completely separate infrastructure and domain-specific privacy policies. They share zero runtime code, storage, or network boundaries with our Atlassian Forge apps.