Oktul home
Contact us

Your data never passes through Oktul's infrastructure

Every Oktul app is built on Atlassian Forge. Atlassian operates the runtime, stores the data and enforces the restrictions you set. No part of Oktul's infrastructure sits between your users and their work.

Atlassian runs the code. We write it

Forge is Atlassian's own app runtime, and every Oktul app is built on it.

Runtime
Atlassian Forge
Data storage
Your Atlassian site
Oktul infrastructure
None

The code runs on Atlassian's compute, and we hold no token of yours

Forge functions run in Atlassian's own environment, isolated per app, under the scopes the app declares at install. We never hold an API token or service account of yours. There is no hosting of ours to assess, and no Oktul outage can affect your apps.

App data sits in Atlassian's database and stays on your site

What an app stores goes in Forge's database, which Atlassian keeps encrypted and isolated to your site. Data that belongs to a work item stays on the work item. If you change your data residency, the data moves with your site.

The manifest lists every host an app may reach, and a proxy enforces it

A Forge app can reach only the hosts named in its manifest. An Atlassian proxy enforces that list on every outbound request, whatever the app tries. You can read the list before you install, and a host added later needs your admin's approval again.

Runs on Atlassian

Atlassian grants this badge automatically to every app that sends no data outside Atlassian and uses Atlassian's storage.

What our apps inherit from Forge's ISO 27001 and SOC 2

Our apps inherit Atlassian's audited controls for the data they keep inside Forge. Forge is ISO/IEC 27001 certified and SOC 2 attested as part of the Atlassian platform. Oktul is not certified yet. We protect the data an app sends out with our own controls.

Of ISO/IEC 27001, mostly Annex A
Up to 20%
Of SOC 2, in three criteria
30%
Management system
Ours

Atlassian and Vanta's estimate of what a Forge app inherits when the audit's scope is the app. The three SOC 2 criteria are Security, Availability and Confidentiality.

AreaWhat Atlassian runsSOC 2ISO/IEC 27001:2022
RuntimeA hardened runtime that an app cannot step outside, scanned for misconfiguration.CC6.6, CC7.1A.8.8, A.8.18, A.8.26
Platform accessOnly authorised Atlassian staff reach the platform and its storage, with strict authentication.CC6.1 to CC6.3A.8.2, A.8.5
Data centresCloud providers with physical protection, access control and redundancy.CC6.4, CC6.5Selected controls in A.7
NetworkTLS 1.2 or higher in transit. A connection must be authorised.CC6.6, CC6.7A.8.20, A.8.21, A.8.24
Logs and monitoringAn audit trail of what an app does, and alerts on health, security and abuse.CC7.2, A1.1A.8.6, A.8.15, A.8.16
StorageAES-256 encryption at rest, with backup and restore.CC5.3, CC6.1, A1.1A.8.10, A.8.12 to A.8.14, A.8.24

Atlassian's mapping in “Forge and compliance with SOC 2 and ISO 27001”, read on 12.11.2026.

What each app inherits

AppWhat it inheritsData residency
Work Item SelectorAll the controls above. The app keeps and processes everything inside Forge.All its data follows your site's data residency.
SignPlusThe controls above, for what the app keeps in Forge. We and the receiving party protect what it sends to the hosts its privacy notice names.Forge storage follows your site's data residency. Data the app sends out does not.
Work Item MacroAll the controls above. The app keeps and processes everything inside Forge.All its data follows your site's data residency.
Regex FieldAll the controls above. The app keeps and processes everything inside Forge.All its data follows your site's data residency.
Code StudioThe controls above, for what the app keeps in Forge. We and the receiving party protect what it sends to the hosts its privacy notice names.Forge storage follows your site's data residency. Data the app sends out does not.

Read from our apps' Forge manifests.

We build the management system ourselves

Forge fulfils none of ISO 27001's clauses 4 to 10 and few of the organisational and people controls in Annex A. We are building that system now and expect certification by March 2027 at the latest.

We secure our code and our people

Under Atlassian's shared responsibility model, we own the app's checks. The app acts as the person whose request it is, validates input, keeps one site's data apart from another's and asks for the narrowest scopes that do the job. Our accounts sit in one directory with multi-factor authentication, and our security scans run before every release.

Forge storage follows your site's location

Atlassian keeps Forge storage in the same location as your Jira or Confluence site and moves it when your admin moves the site. The locations are Australia, Canada, the EU, Germany, India, Japan, Singapore, South Korea, Switzerland, the United Kingdom and the USA, or Global.

Your reviewer can read Atlassian's reports

Atlassian publishes the ISO/IEC 27001 certificate and the SOC 2 report for its platform, Forge included, in its Compliance Resource Center (opens in a new tab). They cover Atlassian's controls. We describe ours in our data processing addendum and our CSA STAR entry below.

Error logs reach us unless you opt out

Atlassian can share logs, analytics and custom metrics from your site with an app's developer, with a switch for each.

Our logs never name a person or their work

Download the logs from your admin settings to see exactly what we receive.

Turn off log sharing in admin.atlassian.com

  1. Go to admin.atlassian.com and select your organisation.
  2. Select Apps, then Sites, then the site you are administering.
  3. Select Connected apps, then the app.
  4. In the Details tab, turn off Logs access, Analytics access and Custom metrics access.
How log sharing works

When you install a Forge app, Atlassian turns on log sharing by default and the developer gets access to that app's logs for your site. It applies to every Forge app on your site, ours included.

Our logs record errors, and the counts and timings of what an app did. They hold no work item or page content and no user records. Atlassian's logging guidelines (opens in a new tab) tell developers not to log names, email addresses, usernames or user-generated content, and we follow them.

What changes when you switch logs off

Marketplace reporting still shows us your licence. The same page downloads the logs, and the audit log keeps your log sharing history. With logs off, we cannot diagnose a fault from our side and ask you for the log file instead, which takes longer.

Our CSA STAR entry and legal documents are public

Everything we commit to is in these documents, ready for your security review. Clause 5.6 of the data processing addendum says how we test each app's code.

CSA STAR Level 1

Oktul is listed in the Cloud Security Alliance STAR Registry at Level 1. We completed the CAIQ Lite questionnaire with all 138 questions, and published it for you or for your security reviewer. Each app's own entry is on its product page.

Read the company assessment (opens in a new tab)

ISO/IEC 27001 certification expected by March 2027

Oktul is implementing an information security management system to ISO/IEC 27001 and expects to be certified by March 2027 at the latest.

Atlassian told within one hour, the Inspectorate within 72 hours

We have had no security breach or incident to date. If one occurs, we tell Atlassian within one hour and, where personal data is affected, the Estonian Data Protection Inspectorate within 72 hours, as the GDPR requires. We rehearse that response once a year, most recently in the last week of October 2026.

Report a vulnerability in the Help Center

Raise it in the Help Center (opens in a new tab), or email support@oktul.com (opens a new email). The Help Center is usually faster, because its form asks for what an email can leave out.

A reply within 24 hours, Monday to Friday

The reply comes from the people who wrote the code. Time to a solution is set per priority. Our security fix times are shorter than Atlassian's bug fix policy for Marketplace apps, which the Atlassian Enterprise Certified programme also applies.

PriorityTime to solutionWhat it means
Critical7 calendar daysThe app is down, or a technical issue is severely blocking the business.
Critical security7 calendar daysA vulnerability scoring CVSS 9.0 or above. An immediate threat to cloud infrastructure or to data.
High security14 calendar daysA vulnerability scoring CVSS 7.0 or above. Significant security exposure with no simple workaround.
Medium security28 calendar daysA vulnerability scoring CVSS 4.0 to 6.9. A moderate security risk.
Low security56 calendar daysA vulnerability scoring below CVSS 4.0. A minor security issue with low potential for exploitation.
Standard support requestNo resolution target. We reply within 24 hours, as we do to every requestA question, a configuration problem, a documentation gap or a feature request. Nothing is broken and nothing is exposed.

What security and procurement teams ask

Do Oktul apps send data outside Atlassian?

Only where a feature has to, such as signing a Confluence page, and then only what that feature needs. Everything else stays in your Atlassian Cloud, because the apps run on Atlassian Forge, not on infrastructure we operate. The app’s documentation names every party that receives data and what it receives.

Is Oktul ISO 27001 certified or SOC 2 attested?

Not yet. We are implementing ISO/IEC 27001 and expect certification by March 2027 at the latest. Our apps run on Atlassian Forge, which is ISO/IEC 27001 certified and SOC 2 attested as part of the Atlassian platform. Atlassian’s audited controls cover the data an app keeps inside Forge. They include the runtime, encryption at rest, backups, the network and who at Atlassian can reach the platform. We protect the data an app sends out with our own controls. The trust page shows what our apps inherit, app by app, and Atlassian publishes its certificate and report in its Compliance Resource Center.

Does app data follow our data residency?

Yes, for everything an app keeps in Forge storage. Atlassian stores it in the same location as your Jira or Confluence site and moves it when your admin moves the site. Data an app sends outside Atlassian is outside your data residency, and the app’s privacy notice names who receives it.

How does Oktul test the security of its apps?

We test them ourselves. Before each release and on the 1st of every month, a workflow in our GitHub organisation scans the code of our apps and this website with Semgrep CE, npm audit, OSV-Scanner, gitleaks and zizmor, plus a type check that finds permission checks nobody awaits. Dependabot watches the dependencies of every repository. Code Studio and SignPlus have web triggers, the one kind of entry point Forge opens to anyone on the internet. We deploy them to a separate Forge environment on our test site and attack the triggers there with OWASP ZAP and our own probe. This website gets a passive ZAP scan. Each app also has a penetration test suite that lists the entry points in its code. We run it by hand before the app’s first release, then every six months and whenever an entry point is new or changed, and its automated checks run with every scan. Before each release we also review the app’s software bill of materials (SBOM): every package added, upgraded or removed since the last review, and every licence that needs reading. We give the SBOM to a customer who asks for it.

Who at Oktul has access, and who can deploy a change?

We hold no account or credential on your site. Our own accounts are managed in one place, Zoho Directory, and every one uses multi-factor authentication. Each access is requested in Jira with a due date, reviewed before that date and removed unless it is extended. Only an app’s admin, usually the owner of its code, runs forge deploy to put a version into production. We are introducing code owner review of every change. Our next security training is in February 2027.

Do Oktul apps send data to an AI model?

No. None of our apps runs an AI model, and none sends your data to one outside Atlassian unless an admin turns that on. Each app’s privacy notice lists every host it may contact. Work Item Selector, Work Item Macro and Regex Field declare none. SignPlus declares Dokobit, its signing provider. Code Studio declares the Git hosts it syncs with, Atlassian’s gateway, and each host a site admin approves for a script. Code Studio’s five agents are Rovo agents, and Rovo is Atlassian’s AI: it reads your Jira and Confluence data under Atlassian’s terms, not ours. Code Studio’s tools also reach Claude or another MCP assistant, but only after an admin turns them on, and what that assistant reads goes to its provider under your agreement with them.

How do Oktul apps give context to Rovo and other AI agents?

They keep the work in Jira and Confluence, where Atlassian’s Teamwork Graph and Rovo look for context. Work Item Selector writes each relationship to a work item property on both work items, which Teamwork Graph reads. Work Item Macro reads Jira live, so a page never carries a stale copy. SignPlus attaches the signed document to the page it was signed from. Code Studio sends each script to Teamwork Graph through a connector, with its own access rules, once an organization admin connects the app. Rovo shows a script only to people who may open it in Code Studio.

How did you check what Rovo and Teamwork Graph do before building for them?

From Atlassian’s own Forge packages and developer documentation, read and dated, then held by tests in our code. Five findings decide what we build. A Forge app either publishes into Teamwork Graph through a connector or queries it, never both. Atlassian accepts a connector only from an app installed into Jira. What a connector sends is visible to everyone on the site unless the app sends permissions of its own, so a connector we build restates the app’s own access and leaves out anything whose access it cannot state. A Rovo agent inside an app reads only through that app’s actions, as the person talking to it. An AI assistant outside Atlassian, such as Claude, reaches an app only through Atlassian’s MCP (Model Context Protocol) endpoint, after an admin turns the app’s tools on. In the apps on this site, Work Item Selector writes each relationship to work item properties, which Teamwork Graph reads. Work Item Macro reads Jira live, as the reader. SignPlus keeps signed documents on the page. Regex Field checks values in Jira. Code Studio’s Rovo agents read as the person talking to them and write drafts only, and its connector publishes scripts to Teamwork Graph with Code Studio’s own permissions. None of them runs an AI model.

Who maintains the apps, and what happens if they stop?

Solution architects named on the About us page, holding twenty-three Atlassian certifications and accreditations together. Oktul OÜ is registered in Estonia under registry code 17589681. The apps run exclusively in your Atlassian Cloud. Atlassian runs the code on its own platform, and your configuration and data stay in your ecosystem whatever happens to us.

How fast do you respond when something breaks?

An initial response within 24 hours, Monday to Friday, on a Help Center request. Raise one in the Help Center, or email support@oktul.com. It takes incidents, bugs, questions, demo and feature requests, and requests for an app we have not built yet.

Why trust Oktul with a bank’s or a ministry’s Atlassian site?

Because we have spent years inside financial, public and private sector Atlassian ecosystems, and our apps solve the problems we met there. They run on Forge, so your Atlassian Cloud depends on no part of our infrastructure.

Is Oktul an Atlassian partner?

Yes. Oktul is an Atlassian Marketplace Partner, with its own partner page on the Atlassian Marketplace.

What does it cost to evaluate one?

Nothing. Every paid Oktul app has a 30-day free trial and is free for up to 10 users. Pricing and billing run through the official Atlassian Marketplace, so the charge lands on your existing Atlassian invoice and there is no new supplier to onboard.

Bring the context together

Start with an app from the Atlassian Marketplace, or tell us which app or Rovo agent is missing.