Less software. More workflow.
Cluware builds focused, Forge-native plugins for Jira and the Atlassian ecosystem. Small footprint, big change — we ship tools that remove friction instead of adding it.
Your Jira data stays in your tenant.
3 lines, not 12.
What we're building
A small, focused catalog. Each plugin does one thing, does it brilliantly, and then stays out of your way.
Plugin One
A quiet standup board that does one thing and disappears.
Plugin Two
Create, link, and ship issues without taking your hands off the keyboard.
Plugin Three
Focus mode for Jira — hides everything but the work that's actually yours.
Four things every plugin we ship has in common.
We turned these into a promise instead of marketing copy. If a future Cluware plugin breaks one, it doesn't ship.
Focused
One job, done brilliantly.
No "suite." Each plugin ships with the minimum surface area needed to solve one specific problem — and nothing else.
Fast
Sub-100ms interactions.
We benchmark every panel and endpoint against stock Jira. If our plugin adds perceptible latency, we ship a fix before the release.
Forge-native
Your Jira data stays in your tenant.
Built on Atlassian Forge. Issue, project, and user data never leave the Atlassian runtime — we inherit their SOC 2 and ISO posture for free.
Honest
Transparent data, visible pricing.
Public scope list per plugin, public subprocessor list, public roadmap for SOC 2 and SSO. Pricing is on the page, not behind a form.
Honestly the first Jira plugin I've installed where I didn't immediately regret it. It just sits there and does one thing well.
Refreshing to see a vendor publish exactly what scopes they're using and why. Passed our security review in one pass.
Feels like someone finally designed a Jira plugin from the keyboard outward.
Security, in plain English.
Most vendors hide behind a badge. We'd rather show you exactly what happens to your data — in a table a human can read.
Via Forge runtime
Runs inside Atlassian's sandboxed infrastructure. Covered by Atlassian's SOC 2, ISO 27001, and regional compliance posture — we never see the data, and we can't.
- Jira issue, project, and user data
- Plugin UI state & user preferences
- OAuth identity (never seen by us)
- Audit events inside your tenant
Only for specific features
Hosted on AWS (region configurable on Enterprise). Encrypted in transit with TLS 1.3 and at rest with AES-256. Every item below is documented, with a reason.
- Anonymized usage metricsProduct improvement · 30-day retention
- License check (instance ID only)Billing · no personal data
- AI inference payloads (opt-in)Only when you enable AI features
No training on customer data · No selling to third parties · DPA available on request
Jira scopes we request
Each plugin installs with the minimum scope set it can get away with.
| Scope | Why |
|---|---|
| read:jira-work | Read issues and projects to render plugin UI |
| write:jira-work | Create or update issues when you explicitly invoke an action |
| read:jira-user | Display assignee avatars and team membership |
| storage:app | Persist plugin state inside your tenant |
Compliance roadmap
We don't claim certifications we don't have. Here's exactly where we are.
- SOC 2 Type IIIn progress · target Q4 2026
- Atlassian Cloud FortifiedSubmitted for review
- SSO / SAML · SCIMShipping on Enterprise plan
- ISO 27001On roadmap
A small studio, on purpose.
Cluware exists because the Atlassian plugin ecosystem has drifted. Most of the big vendors optimized for checkbox parity: every feature your competitor has, plus three more. The result is a decade of plugins that fight you instead of helping.
We're betting in the other direction. We ship small plugins that do one thing brilliantly, stay out of your way, and treat your data like it's yours.
No investor pressure to bolt on a suite. No dashboard of vanity features. Just a handful of well-built tools from a team that uses them every day.
The questions IT and procurement always ask.
If something isn't answered here, email hello@cluware.com — a human will reply.
Do you offer SSO / SAML?
Can we get a DPA?
Where is data stored?
How is pricing structured?
Do you use customer data to train AI?
How do you handle accessibility?
Momentum, in public.
A running log of what's new. The newsletter is a quieter version of the same thing — one email per release, no drip campaigns.