Jira automation, checklists, and time tracking. Built on Forge.

Three apps from one US-based vendor. Your data never leaves Atlassian — we don't even run a server. Free tier on every app at launch.

Coming soon to the Atlassian Marketplace. Email gets you on the early-access list.

Forge-native — no external servers
Can't modify your Jira issues
Free tiers on every app
US-based vendor

Your data stays in Atlassian. Period.

Forge apps run inside Atlassian's infrastructure. There's no middleman server, no external database, no place for data to leak. That's not a marketing claim — it's how the architecture works.

No servers to breach

We don't operate servers, databases, or cloud resources. Your data lives in Forge Storage inside your Atlassian tenant. We literally cannot access it.

Minimal permissions

Our apps don't request the write:jira-work scope. They can't edit your issues, change fields, or modify workflows. That's a security boundary baked into the app manifest.

Zero outbound calls

No analytics pings, no telemetry, no webhooks to external services. Our apps make zero network requests outside Atlassian. Your data has nowhere else to go.

Three apps. One vendor. All Forge.

We're a small team that builds Jira tools we'd actually want to use. Here's what we ship.

Automation

AutomationEngine

Jira automation without writing code or managing an external runtime.

6 trigger types · 8 actions · ready-made templates
  • Trigger on issue create, update, transition, schedule, or webhook
  • Actions: assign, comment, change status, link issues, send notifications
  • Condition builder with AND/OR logic and JQL filters
  • Pre-built templates for common workflows
  • Audit log for every rule execution
  • No scripting. No Groovy. No external compute.
Get AutomationEngine Early Access

Free tier at launch: 5 active rules

Checklists

ChecklistPro

Checklists that actually enforce your process — not just decorate your issues.

Workflow validator blocks transitions until items are checked
  • Add checklists via issue panel — no custom fields needed
  • Checklist templates applied by issue type or project
  • Mandatory items with assignees and due dates
  • Workflow validator: block "Done" until checklist is 100%
  • Progress tracking across sprints and projects
  • Definition-of-done enforcement, built in
Get ChecklistPro Early Access

Free tier at launch: 5 checklist items per issue

Time Tracking

TimeTracker Pro

Track time in Jira without paying $5/user/month for it.

Start/stop timer · approval workflows · CSV export
  • One-click timer or manual entry on any issue
  • Billable vs. non-billable categorization
  • Manager approval workflow for submitted hours
  • Project and team reports with CSV/XLSX export
  • Expense categories for multi-client billing
  • All data stored in Forge — not on our servers
Get TimeTracker Pro Early Access

Free tier at launch: 5 users, no approvals or exports

Coming from somewhere else?

We get it — switching tools is a pain. Here's why people make the move.

ScriptRunner → AutomationEngine

No code. No scripts. No external runtime.

ScriptRunner is powerful, but most teams use 10% of it and spend hours debugging Groovy. AutomationEngine gives you triggers, conditions, and actions in a visual builder — and runs on Forge instead of Connect.

~45% lower cost

Tempo → TimeTracker Pro

Same workflow. 40% less on your invoice.

Timer, manual entry, approval flows, reports, CSV export. The features you actually use in Tempo, without the features you're paying for but never touch. And your data stays entirely in Atlassian.

~40% lower cost

HeroCoders → ChecklistPro

Checklists that block transitions.

HeroCoders gives you checklists. We give you checklists with a workflow validator that prevents issues from moving to "Done" until every required item is checked. That's the difference between decoration and enforcement.

~37% lower cost

JMWE → AutomationEngine

Built on Forge. Not on borrowed time.

JMWE runs on Atlassian Connect, the older framework where apps host their own servers. Atlassian is investing heavily in Forge — their newer platform where apps run inside Atlassian's own cloud. We built on Forge from day one.

No external servers in your stack

Transparent pricing. No surprises.

Every app has a free tier. No credit card required. Pay annually and get 2 months free.

AutomationEngine

Jira automation, no-code

Free: up to 5 active rules
1–10 users$10/mo flat
11–100 users$1.75/user/mo
101–1000 usersVolume pricing
1001+ (Enterprise)2× Standard + SLA
Get Early Access

ChecklistPro

Checklists with workflow enforcement

Free: up to 5 items per issue
1–10 users$10/mo flat
11–100 users$1.50/user/mo
101–1000 usersVolume pricing
1001+ (Enterprise)2× Standard + SLA
Get Early Access

TimeTracker Pro

Time tracking with approvals

Free: up to 5 users
1–10 users$15/mo flat
11–100 users$3.00/user/mo
101–1000 usersVolume pricing
1001+ (Enterprise)2× Standard + SLA
Get Early Access

Annual billing saves 2 months. Enterprise tier includes SLA, priority support, and annual invoicing. All prices in USD.

The math on time tracking

If your team bills clients or tracks project costs, the numbers are pretty clear.

$3
per user / month
(at 100 users)
1 hr
recovered per user / week
(typical with proper tracking)
70×
return on cost
(at $50/hr billing)
Example: 50-person agency billing at $75/hour TimeTracker Pro costs $150/month for 50 users. If proper time tracking recovers just 30 minutes per person per week of previously unbilled time, that's 100 hours/month × $75 = $7,500 in recovered revenue. Your cost is $150. That's a 50:1 return before you count the reduced admin time from approval workflows.

We designed for the security review.

We built these apps knowing they'd face procurement reviews at serious companies. Here's what your security team will find.

No external data processing

All app logic runs inside Atlassian's cloud. We don't operate infrastructure, so there's nothing to audit beyond the app manifest.

Minimal scopes

We request only the permissions we need. Notably absent: write:jira-work. Our apps read issue data to render panels and checklists — they don't modify your issues.

Data residency

Your data is stored in Forge Storage, which inherits your Atlassian data residency settings. If your Jira data lives in the EU, so does your NovaCraft Tools data.

Vendor consolidation

Three tools, one vendor. One security review covers all three apps. One procurement process. One vendor to manage. That matters when you're managing 40+ Marketplace apps.

US-based vendor

NovaCraft Tools is a US-based company. US legal jurisdiction for contract disputes and data subject requests, US business hours for support, and a familiar W-9 / 1099 trail for procurement. Most established competitors in this space are based in the UK, Iceland, or EU.

Security questionnaire support

We respond to vendor security questionnaires (CAIQ, SIG, custom) within 5 business days. The Trust & Security page already answers most of what your security team will ask — scope, data handling, encryption, compliance posture.

Questions we actually get asked

It means our apps run entirely inside Atlassian's infrastructure — not on our servers. We don't have servers. Your data is stored inside your Atlassian tenant, processed within Atlassian's cloud, and never sent anywhere else. For your security team, it means there's no third-party infrastructure to evaluate.
The free tiers are permanent, not time-limited trials. AutomationEngine gives you 5 active rules. ChecklistPro gives you 5 items per issue (without the workflow validator). TimeTracker Pro covers up to 5 users without approvals or CSV export. Small teams can use these indefinitely.
We're preparing to launch on the Atlassian Marketplace. Email [email protected] to get on the early-access list — we'll notify you with a direct install link as soon as the apps are live. Once on the Marketplace, you install through Atlassian and billing runs through your Atlassian account: the Marketplace handles payments, invoicing, and license management. Enterprise customers (1001+ users) get annual invoicing, an SLA, and priority support.
Once we're on the Marketplace (or you've joined early access), install our app, set up your rules/checklists/timers, and run it alongside your current tool. There's no data migration needed — our apps create their own data structures in Forge Storage. Most teams run both tools in parallel for a sprint or two, then sunset the old one. The free tier makes it zero-risk to try.
It's a Jira workflow validator that prevents status transitions (like moving to "Done") unless all required checklist items are checked. This turns checklists from a nice-to-have into actual process enforcement. You configure which transitions require complete checklists, and Jira blocks the move until the criteria are met. No workarounds.
Currently, all three apps are built for Jira Cloud. JSM support is on our roadmap. If you need JSM or Confluence integration, email us at [email protected] — it helps us prioritize.
Email [email protected]. Standard support targets a 48-hour response. Enterprise customers get a 4-hour response SLA for critical issues. We're a small team and we read every message ourselves — you won't get a chatbot.

Get on the early-access list.

We're preparing to launch on the Atlassian Marketplace. Email us and we'll notify you with direct install links the moment the apps go live. Free tier ready on day one.

Email Us for Early Access