Pricing
Simple pricing. You pay for active users only.
Start free or try Team for 14 days. Users are active people and pending invitations; view-only people are free on every plan.
Free
For small teams trying IT4S.
- Up to 3 users and 3 projects
- Up to 10 viewers for free
- 1 GB storage, files up to 10 MB
- 2,000 API and MCP calls per day and workspace
- All features incl. MCP and Jira import
- Nightly backups, kept 7 days
- Help via docs and email
Team
Try free for 14 daysFor teams who work in it every day.
- Unlimited users and projects
- Unlimited viewers for free
- 10 GB storage per user, files up to 250 MB
- 20,000 API and MCP calls per user and month
- Nightly backups, kept 30 days
- Email support, answer within 2 business days
- Pay by card or SEPA direct debit
Guided start
When you want to make the move with us.
- Guided move from Jira and Confluence
- Workspace setup with your team
- Connecting your AI agents, such as Claude or Cursor
- AI enablement workshop by Silvertip
Prices in EUR excl. VAT. IT4S is for businesses of any size, including self-employed people and freelancers. We do not offer accounts for private use (Terms). EU businesses outside Austria with a VAT ID pay no VAT (reverse charge).
When users join or leave, the difference is charged or credited pro rata once a month. Price changes are announced 60 days ahead.
API and MCP calls: Free counts per workspace and day, Team per user and calendar month; the counter starts again at midnight or on the first of the month (the workspace’s time zone).
Moving from Jira
Your keys stay.
Connect Jira, check the analysis, import. Issues, comments, worklogs, attachments and the field history come along – and WEB-12 is still WEB-12 afterwards. Links to Jira issues now open in IT4S.
How the import works →Example numbers from the demo workspace. By default the import creates a new project with the Jira key; with another key, WEB‑12 becomes HP‑12 for example – in titles, descriptions and comments too.
Calculator
What does IT4S cost for your team?
Active people and pending invitations count as users. When users join or leave, the difference is settled pro rata once a month.
Prices in euros, excl. VAT. Viewers don’t count.
Compared to Jira
Less to configure. Less to click. More time for the work.
Jira can be set up for almost anything, and someone has to do that setup. IT4S makes the common choices for you, so a new project takes a key, a name and its members.
A new project in IT4S needs a key, a name and its members. Done.Each of them needs looking after – by someone with admin rights.
- 01Pick a project template
- 02Work type scheme
- 03Workflow scheme
- 04Workflow with transitions and conditions
- 05Screen scheme
- 06Work type screen scheme
- 07Field configuration
- 08Field configuration scheme
- 09Permission scheme
- 10Notification scheme
- 11Board filter in JQL
- 12Board column mapping
New projectExample of a company-managed project in Jira; which schemes you need depends on your instance.
One epic, twelve stories
The race.
On the left, one form per story. On the right, one sentence to your AI agent.
12 forms. Or one sentence.
| Typical Jira setup | IT4S | |
|---|---|---|
| Workflow | Workflow schemes per project, kept in shape by an admin | Backlog›To Do›In Progress›In Review›Done The same in every project, plus Won’t Do. |
| New project | Pick templates, schemes, screens and field configurations | Key, name, members. Ready. |
| Finding issues | JQL or, in the cloud, AI search with Rovo | Filter chips and a quick search with AND, OR and NOT that also searches comments, or ask an AI agent like Claude in plain words |
| Board | One board per project or filter | One board across all projects with a project filter |
| A batch of stories from a spec | One create form per story | One sentence to your AI agent with plan_epic; up to 50 issues per call |
| Keeping track | A notification per change, dashboard gadgets | “Since your last visit” on every issue, project briefing, daily digest |
| Connecting AI assistants | Official Rovo MCP server for Atlassian Cloud; not for Data Center | Built in on every plan, for any MCP-capable agent, run in the EU, traceable in the history (“via Claude”, “via Cursor”), with trash |
| Where your data lives | Atlassian Cloud or your own Data Center | Google Cloud in Frankfurt, run by Silvertip in Austria |
| Moving over | Your existing projects and history | Issues, comments, files, worklogs and field history from Jira, keys kept Available |
Left out on purpose
Every feature you skip is a setting nobody has to maintain. These are not in IT4S; sprints are the most likely to come next.
- Workflow schemes
- Permission schemes
- Custom field sprawl
- Query language
- Dashboard gadgets
- Sprints and burndown planned
Billing questions
More answers in the help section.
Who counts as a user?
Active people and pending invitations, customers too. Viewers, who only read, are free.
How do we pay?
By card or SEPA direct debit through Stripe. Changes in users are settled pro rata once a month.
VAT?
Prices excl. VAT. IT4S is for businesses; with a VAT ID from another EU country, reverse charge applies.
What happens at a limit?
Nothing new can be added, nothing is deleted. API and MCP calls count per day on Free, per user and calendar month on Team.