First app live on the Atlassian Marketplace

Apps for the tools your team already runs

Dripwork builds small, focused apps that each do one job well. Mostly the job is stopping a routine change from quietly breaking something downstream.

See the apps Talk to us

One job per app. Narrow permissions. Plain answers.

The apps

Small tools for the changes that bite

Every app does one job, asks for the narrowest permission that job needs, and tells you plainly what it can and cannot see. One is live, one is in review, one is in development, and others are in progress.

Jira Cloud Atlassian Forge Free Available now

Work Type Guardrails for Jira

Puts guardrails on work type changes. Admins define which work type transitions are allowed per project, and the app blocks the ones that aren't. It stops the change as someone makes it, rather than listing it in a report afterwards.

  • Per-project rules for which work type transitions are allowed
  • Blocks a disallowed change as it happens, rather than flagging it later
  • Built on Atlassian Forge, so it runs on Atlassian's own infrastructure
  • Free, with no seat tiers
Get it on the Marketplace Learn more
monday.com $1 / seat / month 14-day trial

WhereUsed for monday.com

A Mirror on another team's board, or a Formula that calls a column by name, can stop working the moment you change it, and nothing warns you first. WhereUsed maps those links before you rename or delete anything.

  • Traces Mirror, Formula and Connect Boards dependencies
  • Account-wide overview of which boards lean on which
  • Daily scan with alerts for columns deleted or renamed since your last visit
  • 30 days of history, plus CSV and JSON export
  • One permission: read boards. It never reads your items or their values
In review on the monday.com marketplace whereused.app
Jira Cloud Atlassian Forge Read-only

Lookahead: Read-only Gantt for Jira

A plan can look sound in each project and still be impossible once the dependencies between them line up on one axis. Lookahead puts work from any set of projects on a single Gantt timeline and marks the places where the dates cannot hold.

  • One timeline across many projects, a saved filter or any JQL
  • Blocks dependencies drawn as arrows, red where a schedule conflicts
  • Dates taken from your own fields, sprints and fix versions, never invented
  • Saved views, shared or personal, plus CSV and image export
  • No write permission at all, so the app cannot change your Jira data
In development Learn more

More on the way

Dripwork is the home for everything we publish, whatever tool it plugs into. New apps land here first. Tell us what keeps breaking in your setup and it may well be the next one.

Suggest an app
How we build

Narrow scope, plain answers

These apps sit inside the system your team plans its work in. That's a good reason to keep them small and to be exact about what they touch.

Least privilege

Each app asks for the narrowest permission that does the job, and the listing says what that permission can and cannot reach.

Structure, not content

Our apps work on configuration, such as board, column, project and work type settings, rather than the contents of your team's items and issues.

Your own access

Nobody sees more through our apps than they could already see in the host tool. Reports follow the permissions the person already has.

No false comfort

A scan reports what it covered. "Nothing found" means the scan found nothing, never that nothing exists, and we say so in the product.

Contact

Get in touch

Questions about an app, a bug, a feature you need, or a partnership. All welcome.

General enquiries

Anything about Dripwork, the apps, or working together.

hello@dripwork.dev

Support

Trouble with an installed app, or a question about how one behaves.

support@dripwork.dev