Your data never passes through Oktul's infrastructure

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 ecosystem, because the applications run on Atlassian Forge, not on infrastructure we operate. The application’s documentation names every party that receives data and what it receives.

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 applications 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 application also has a penetration test suite that lists the entry points in its code. We run it by hand before the application’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 application’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.

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 application’s administrator, 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.

No. None of our applications runs an AI model, and none sends your data to one outside Atlassian unless an administrator turns that on. Each application’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 administrator 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 administrator turns them on, and what that assistant reads goes to its provider under your agreement with them.

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 the 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 the Teamwork Graph through a connector, with its own access rules, once an organisation admin connects the app. Rovo shows a script only to people who may open it in Code Studio.

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 the 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 application’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 administrator turns the app’s tools on. In the applications on this site, Work Item Selector writes each relationship to work item properties, which the 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 the Teamwork Graph with Code Studio’s own permissions. None of them runs an AI model.

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 applications run exclusively in your Atlassian ecosystem. Atlassian runs the code on its own platform, and your configuration and data stay in your ecosystem whatever happens to us.

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 application we have not built yet.

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

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

Nothing. Every paid Oktul application 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.