The people who answer are the people who wrote it.
An Estonian software company building applications for the Atlassian platform, founded in 2026 by solution architects out of their own consulting practice. That practice is still where the roadmap comes from: the gaps we build against are gaps we found on somebody else's implementation first.
Why buy production software from a company this size?
It is the right question and we would rather answer it here than have it raised in a procurement meeting we are not in. There are three parts to the answer, and the first is the one that does most of the work.
There is no Oktul server between you and your data.
The applications run on Atlassian Forge, inside your own Atlassian instance. Atlassian operates the runtime, holds the data and enforces the permissions, so the usual small-vendor risk — an unfunded startup running infrastructure your production system depends on — does not exist here. Your configuration and your data stay in your instance whatever happens to us.
An initial response within 24 hours, from the architects.
No first-line tier to get through and no triage that ends with your question restated back to you. The person who reads your report wrote the code it concerns, which is the one operational advantage a team this size genuinely has over a large vendor.
Twelve Atlassian credentials, each with a date.
The designations and certifications are listed below with the month each was awarded, so any of them can be checked against Atlassian's own directory. Where a credential is retired we say so rather than quietly leaving it in: retired means it remains valid and is no longer awarded to new candidates.
Designations and certifications, with the month each was awarded.
The twelve senior credentials behind the applications: the Atlassian designations and the examined certifications. Every entry can be verified through Atlassian's own credential directory, which is why the dates are here. Accreditations, product credentials and degrees are in the footnote under each name.
A credential marked retired remains valid but is no longer awarded to new candidates. Dates are the month awarded, not the month of expiry.
The experience behind the applications.
Every figure here is about the company. Test counts, Forge scopes and egress answers are per application, and are published on each application's own page.
- Hours implementing the Atlassian platform
- 14,000+
- Combined across the team, on public and private sector programmes before the first product shipped.
- Years each, in Atlassian delivery
- 7+
- Jira and Jira Service Management administration, migrations and platform integration.
- Atlassian certifications and accreditations
- 23
- Designations, certifications, accreditations and credentials. The company page lists the designations and certifications, each with the month it was awarded.
Work with banks in several countries set the standard.
Both of us spent years inside financial and public sector Atlassian instances, where an application that mishandles a field is a change-control incident rather than an inconvenience. That is where the release practice comes from: automated application, injection and security suites run before every release, security and privacy are release criteria rather than a later hardening pass, and compatibility is tested before it is promised.
Where a claim has a number behind it, the number is on the application's page. Where it does not, we say what the practice is and leave the adjective out.
- Registered name
- Oktul OÜ · Oktul LLC in English
- Registry code
- 17589681
- Registered office
- Tallinn, Harjumaa, Estonia
- Founded
- 2026
- Partnership
- Atlassian Marketplace Partner
- Contact
- hello@oktul.com
Oktul is an Atlassian Marketplace Partner and our applications follow the Atlassian Design System. We do not claim to be recommended or endorsed by Atlassian. Where Atlassian has granted an application a programme badge, that badge appears on that application's page, because it is awarded per application.
- assessed hundreds of applications for clients before we built our own
- Senior consultants
- the applications run inside your own Atlassian instance, on Atlassian’s infrastructure, never on ours
- Not our servers
- the person who answers your ticket is the one who wrote the code
- Ready to support