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
From client request to production release, in one place.
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.
- £0 for up to 5 users
- £80/month for up to 50
- Free Jira & Confluence import
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
- Issue tracking
Jira - Client service desk
Jira Service Management - Wiki
Confluence - Incident updates
Statuspage
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.
Built for working with clients
A client portal, client-visible incident updates and release notes, and clients only ever see what you choose to share.
One flat price
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 requests. Developers work the same ticket.
Every client gets a secure portal to raise, prioritise and follow requests. Your team picks up the same ticket on the board, with internal notes kept out of the client’s view.
More about Support & client portalYour requests
New request| Ticket | Request | Status |
|---|---|---|
| NW-142 | Add PO number to the invoice export | Released |
| NW-147 | Driver app: show depot phone number | Scheduled |
| NW-150 | Date picker resets on Safari | Investigating |
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
Boards that keep the process honest
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 & workflowAll typesSupportEpicPriorityAll active sprints
Backlog2
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
Commits, pull requests and deployments on the ticket
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
Incidents that open, update and close themselves
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 & uptimeSEV2
Checkout returning 502 errorsCommander: Sam Okafor · Linked: deploy v2.4.0
- Investigating
Uptime check on /checkout failed 3 times in a row. Incident opened automatically.
- Identified
Cause found in v2.4.0 payment timeout setting. Rolling back.
- Monitoring
Rolled back to v2.3.9. Client update sent to 4 subscribers.
- Resolved
Five consecutive successful checks. Resolved automatically.
Wiki
Documentation next to the work it describes
Nested pages, version history, ticket links and per-space permissions. Search covers the wiki, tickets and client conversations at once.
More about Wiki & knowledge base- Northwind Portal
- Architecture
- Runbook: deployments
- Client contacts
- Engineering handbook
- Support playbook
Runbook · 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.
Linked tickets: NW-139 NW-142
Reporting
Delivery health for every project
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.
What the Atlassian stack costs compared with Jonta
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 | Atlassian costs |
|---|---|---|---|
| 20 people5 handling support | $415.20about £313 | £80Pro, flat | 3.9× as much |
| 50 people10 handling support | $1,014.50about £765 | £80Pro, flat | 9.6× as much |
Atlassian figures: Jira Standard $7.91 and Confluence Standard $6.40 per user, JSM Standard $20 per agent, Statuspage Hobby $29 or Startup $99 per month. Converted at $1 = £0.7537 (7 October 2026). Prices checked 8 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.
Pricing
Every feature on every plan
You only choose how many people need access. Pro works out at £1.60 per user with a full team of 50.
Free
Up to 5 users
£0free, for good
No card needed
Every feature, for small teams and for trying Jonta with real clients.
Get started freeMost teams choose Pro
Pro
Up to 50 users
£80
£72
per month
for the whole team
for the whole team
Billed monthly, or £864 a yearBilled yearly at £864
One flat price for your whole team. No per-user charges.
Get startedEnterprise
51 to 150+ users
£500
£450
per month
for the whole team
for the whole team
Billed monthly, or £5,400 a yearBilled yearly at £5,400
For larger organisations, with new features built into Jonta for your system.
Talk to usPrices exclude VAT. Prices updated 8 October 2026.
Free migration
Leave Jira. Keep your history.
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
Common questions
How much does Jonta cost?
Jonta is free for up to 5 users. Pro is £80 a month for up to 50 users, and Enterprise is £500 a month for 51 to 150+ users. These are flat prices for the whole workspace, not per user. Prices exclude VAT.
Is Jonta priced per user?
No. Every plan is one flat price for the workspace. Pro costs £80 a month whether you have 6 users or 50.
Does Jonta replace Jira Service Management and Confluence?
For many software agencies and development teams, yes. Jonta includes ticketing with a client portal, sprints and boards, a wiki, release notes, incident management and uptime monitoring in one product.
Can we move from Jira and Confluence?
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.
Can our clients use Jonta?
Yes. Clients get a secure portal to raise and track requests, talk to your team, see releases and follow incidents. They only see information made available to their company.
From the blog
Guides for client-facing software teams
Jira alternatives for agencies that support clients
The best Jira alternatives for software agencies in 2026: what each tool does well, what it costs per month, and which ones give clients a portal.
Read the guideJonta vs Jira: cost and features for small teams
Jonta vs Jira for teams of 10 to 50: what each costs per month with a client portal, wiki and status updates, and which features each includes.
Read the guideHow to run support and development in one tool (without Jira Service Management)
A practical guide to running client support and development in one tool: one ticket per request, a client portal, workflow rules and release notes.
Read the guide