One ticket, request to release
The client’s request is the development ticket, then the commit, the deployment and the release note. Nothing is copied between tools.
For software teams that support clients
Jonta brings support tickets, sprints, GitHub, deployments, release notes, incidents and your wiki into one platform. One flat price for the whole team, not per user.
NW-142
ReleasedAdd PO number to the invoice export
Raised in the client portal
Ellie Grant, Northwind Logistics
Moved to In Progress
Assigned to Priya Shah
PR #318 opened
feat: PO number on invoice export · CI passing
Deployed to production
v2.4.1 · commit 8c41e2a · succeeded
Release notes sent
Emailed to 3 Northwind contacts and published in the portal
One product instead of four
All included in Jonta
What is Jonta?
Jonta is a platform for software agencies and development teams that brings client support, development, project planning, releases, incidents and internal knowledge together. Each client request becomes a trackable ticket, from the first report through to deployment and the release note, and every feature is included at one flat price for the whole team.
The client’s request is the development ticket, then the commit, the deployment and the release note. Nothing is copied between tools.
A client portal, client-visible incident updates and release notes, and clients only ever see what you choose to share.
No per-user maths. The wiki, client portal, incidents and uptime monitoring are on every plan, and migration from Jira is free.
Support
Clients raise tickets in their own portal or by email. Each one lands on a Support board for triage, shows the client status names you choose, and moves to the development board as the same ticket, with internal notes kept out of the client’s view.
More about Support & client portalService status All projects are operational
My tickets
New ticket| Ticket | Title | Status |
|---|---|---|
| NW-142 | Add PO number to the invoice export | Resolved |
| NW-147 | Driver app: show depot phone number | In progress |
| NW-150 | Date picker resets on Safari | Waiting on you |
NW-147 · Conversation
Ellie GrantCould the depot number show on the delivery screen too?
Priya ShahYes, that’s in this sprint. We’ll post the release notes here when it’s live.
Boards
Per-project columns with client-facing names, real-time updates, swimlanes, WIP limits and workflow rules that block or warn before a ticket skips a step.
More about Boards & workflowBacklog2
NW-150
Date picker resets on Safari
NW-151
Bulk export of delivery notes
To Do1
NW-147
Driver app: show depot phone
In Progress1
NW-142
Add PO number to invoice export
In Review1
NW-139
Upgrade payment SDK
Awaiting client test0
No tickets
Delivery
Mention a ticket key and GitHub activity links itself. CI reports each deployment with its environment, version and the tickets it shipped, ready for release notes.
More about GitHub & deployments| Environment | Version | Status | Included | When |
|---|---|---|---|---|
| Production | v2.4.1 | Succeeded | 6 tickets | Today 14:22 |
| Staging | v2.4.1 | Succeeded | 6 tickets | Today 12:10 |
| Production | v2.4.0 | Rolled back | 4 tickets | Mon 09:55 |
| Staging | v2.4.0-rc2 | Failed | 4 tickets | Fri 16:31 |
PR #318 feat: PO number on invoice export Merged CI passing
Incidents
Uptime checks open an incident after repeated failures, the commander posts internal and client-visible updates, and the incident resolves when the site recovers.
More about Incidents & uptimeCheckout returning 502 errorsCommander: Sam Okafor · Linked: deploy v2.4.0
Uptime check on /checkout failed 2 pings in a row. Incident opened automatically at Sev 2. Admins emailed.
Cause found in v2.4.0 payment timeout setting. Rolling back.
Rolled back to v2.3.9. Client notified by email.
Two consecutive HTTP 200 responses. Resolved automatically.
Wiki
Nested pages, version history, ticket links and per-space permissions. Search covers the wiki, tickets and client conversations at once.
More about Wiki & knowledge baseRunbook · edited by Tom Ellis · version 7
Deploying the Northwind Portal
Production deploys run from CI after a tagged release. Check the incident board before deploying on a Friday.
Reporting
Deployment frequency, lead time, change failure rate and time to restore, worked out from the tickets, commits, deployments and incidents already in Jonta.
More about Reporting & DORA metricsDeployment frequency
4.2 / weekHighLead time for changes
1.8 daysHighChange failure rate
12%MediumTime to restore
39 minHighIndicative bands. Example data.
A typical client-facing team on Atlassian pays for Jira, Confluence, Jira Service Management and a status page, each priced separately. Monthly list prices, Standard plans.
| Team | Jira + Confluence + JSM + Statuspage | Jonta | Jonta saving |
|---|---|---|---|
| 20 people5 handling support | $500.50about £377 | £50Pro, flat (£25 for the first 6 months) | 87% less |
| 50 people10 handling support | $1,210.50about £912 | £50Pro, flat (£25 for the first 6 months) | 95% less |
Atlassian figures: Jira Standard $9.70 and Confluence Standard $7.15 per user, JSM Standard $26.90 per agent, Statuspage Hobby $29 or Startup $99 per month. Converted at $1 = £0.7537 (7 October 2026). Prices for these team sizes checked on Atlassian’s pricing pages on 15 October 2026; see our comparison sources. Atlassian’s free plans cover teams of up to 10 users, so for very small teams the saving is smaller. Prices exclude VAT.
Jira, Confluence, Jira Service Management and Statuspage are trademarks of Atlassian. Jonta is not affiliated with or endorsed by Atlassian.
Pricing
You only choose how many people need access. Pro works out at £1 per user with a full team of 50.
No card needed
Every feature, for small teams and for trying Jonta with real clients.
Get started freeMost teams choose Pro
for your first 6 months, then £50 a montha month in year 1, then £45 a month
Billed monthly. 10% off yearlyBilled yearly: £405 for year 1, then £540 a year
One flat price for your whole team. No per-user charges.
Get startedfor your first 6 months, then £300 a montha month in year 1, then £270 a month
Billed monthly. 10% off yearlyBilled yearly: £2,430 for year 1, then £3,240 a year
For larger teams that need more users, client users and storage, at one flat price.
Get startedFrom
for your first 6 months, then from £598 a month
Monthly or yearly billing
For organisations with more than 100 users, more than 500 client users or more than 50 GB of storage.
Talk to us* Price agreed with you.
Introductory prices apply to every new workspace for its first 6 months, then the standard price applies. Prices exclude VAT. Prices updated 5 November 2026.
Free migration
Import Jira projects and Confluence spaces for free. Ticket numbers, comments, attachments, sprints, custom fields and original authors come with you, and you can dry-run the import before switching over.
ConnectJira Cloud API · 4 projects found
MapStatuses, ticket types, users and custom fields
Dry run12,480 tickets · 0 errors · numbers preserved
ImportNW project · 8,214 of 12,480 tickets
Switch overRe-run to pick up changes without duplicates
Jonta is free for up to 10 users. Pro is £25 a month for your first 6 months, then £50 a month, for up to 50 users, and Pro+ is £150 a month for your first 6 months, then £300 a month, for up to 100 users. For more than 100 users, Enterprise is from £299 a month for your first 6 months, then from £598 a month, with the price agreed with you. These are flat prices for the whole workspace, not per user. Prices exclude VAT.
Yes. Every new workspace pays the introductory price for its first 6 months: £25 a month for Pro and £150 for Pro+. After 6 months the standard price applies: £50 a month for Pro and £300 for Pro+. The Free plan stays free.
For many software agencies and development teams, yes. Jonta includes ticketing with a client portal, Support boards and tickets by email, sprints and boards, a wiki, release notes, incident management and uptime monitoring in one product.
Yes, free on every plan. Jira projects and Confluence spaces can be imported through the API or from backup and export files, keeping ticket numbers, comments, attachments, sprints, authors and timestamps.
Yes. Clients get a secure portal, or can use email, to raise and follow tickets and talk to your team. They see service status, release notes and the wiki pages you share, in status names you choose, and only ever see their own organisation’s tickets.
From the blog
How agencies can generate client release notes from the tickets they shipped, write them in plain words, and send them by email and the client portal.
Read the guideWhat an agency should monitor on each client website, how often to check it, and how to turn repeated failures into an incident clients hear about first.
Read the guideWhat the DORA metrics measure, the 2024 benchmark bands, and a practical way for a small agency or in-house team to track them without extra tooling.
Read the guideFree for up to 10 users
Every feature on every plan. After that, Pro is £25 a month for your first 6 months, then £50 a month, flat for up to 50 users, and migration from Jira and Confluence is free.