# Oktul

> We ran Atlassian Cloud before we built apps for it. We build Atlassian Cloud applications for banks, ministries and enterprises. Each began as a gap we hit running somebody else’s Jira.

Oktul OÜ · Reg. nr 17589681 · Tallinn, Harjumaa, Estonia. English rendering: Oktul LLC. Contact: hello@oktul.com.

Oktul is listed in the CSA STAR Registry at Level 1, a published CAIQ Lite self-assessment
covering the company: https://cloudsecurityalliance.org/star/registry/oktul-llc/services/oktul-llc. It is a self-assessment rather than an audit.

Every page below is also served as markdown at the URL shown. Those files are
generated from the same content as the HTML, so they cannot disagree with it.

## Start here

- [Atlassian Cloud apps built by Atlassian architects](https://oktul.com/index.md): what Oktul builds and for whom.
- [Trust and data handling](https://oktul.com/trust/index.md): where the software runs, what data leaves an Atlassian instance, the support commitment with its four resolution targets, and how to report a vulnerability. This is the page to read for a security or procurement question.
- [Company and credentials](https://oktul.com/about/index.md): who maintains the software, with every Atlassian credential and the month it was awarded.
- [Atlassian Cloud applications](https://oktul.com/apps/index.md): the applications Oktul publishes.
- [Contact and support](https://oktul.com/contact/index.md): the support portal, what can be raised there, and the one published address.

## Applications

- [Work Item Selector for Jira Cloud](https://oktul.com/apps/work-item-selector/index.md): Allow users to select work items based on Jira Query Language (JQL). Host: Jira Cloud.
  - Documentation: https://oktul.com/docs/plugins/work-item-selector/install/
  - Runs on Atlassian: granted by Atlassian to applications that store data only
    inside Atlassian and declare no external permissions. Per application, not company-wide:
    https://developer.atlassian.com/platform/marketplace/runs-on-atlassian/
  - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138
    questions, published by the Cloud Security Alliance. A self-assessment rather than an
    audit, and nine of the answers are no: https://cloudsecurityalliance.org/star/registry/oktul-llc/services/work-item-selector-for-jira-cloud-issue-picker

## Documentation

- [Work Item Selector documentation](https://oktul.com/docs/plugins/work-item-selector/install/)

## Support

- [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals): the support portal. Public, no account needed. Incidents,
  bugs, questions, demo requests, feature requests, requests for an application not yet built,
  partner requests, and vulnerability reports. A first response inside one business day, Monday
  to Friday, measured against the request. Runs on Jira Service Management with EU data residency.
- support@oktul.com: the same service desk reached by email, so a message here opens a request
  with a reference and the same response target. The route for a vulnerability report when a
  portal is not wanted, though the portal is preferred.
- hello@oktul.com: read by a person, and where a data protection request goes. Not where the
  response target is measured.

## Questions Oktul is asked

- **Where does our data go when we install an Oktul application?** Data stays inside Atlassian wherever the feature allows, because the applications run on Atlassian Forge inside your own Atlassian instance rather than on infrastructure we operate. Where a feature genuinely requires data to leave, only the minimum leaves, nothing is retained by anyone downstream, and every partner in that path is named on that application’s page. That answer is decided per application, so the page for the application you are evaluating states it in full before you install.
- **Who maintains the applications, and what happens if they stop?** Two named solution architects, holding twenty-three Atlassian certifications and accreditations between them, each listed on the company page with the month it was awarded. Oktul OÜ is a registered Estonian company, not an alias. The applications run on Atlassian Forge, which means there is no Oktul-operated server for your instance to depend on: the code runs in Atlassian’s runtime, and your configuration and data remain in your instance whatever happens to us.
- **How fast do you respond when something breaks in production?** An initial response within 24 hours, Monday to Friday, on a request raised in our Help Center. Raise it there rather than by email: a request in the portal has a type, a reference and a response target measured against it, and an email has a person reading it and nothing measuring it. The portal is public, needs no account and no Atlassian licence, and asks only for an email address so the reply has somewhere to go. It takes incidents, bugs, questions, demo requests, feature requests and requests for an application we have not built yet, and partners have their own request types. Support is answered by the people who wrote the code, so there is no tier to escalate through before reaching someone who can read the stack trace.
- **Why would we trust a small vendor with a production Jira?** Because of where the software runs and what we publish about it, not because of our size. Forge means the application has no server of ours in its path and no credentials of yours in our custody. Every claim we make is checkable: the certifications are listed with dates, the response time is a written SLA, and each application publishes its scopes, storage and egress before you install it. We also state limitations next to the features they bound, which is the part a vendor with something to hide leaves out.
- **Is Oktul an Atlassian partner?** Oktul is an Atlassian Marketplace Partner, and we say so at first mention in every material rather than implying a broader relationship. We are not claiming an Atlassian endorsement of any individual application beyond the programme badges Atlassian itself grants, and where an application has been granted one, that badge appears on the application’s own page because it is awarded per application.
- **What does it cost to evaluate one?** Pricing, trials and billing all run through the Atlassian Marketplace, on the same terms as every other app in your instance. So the application appears on your existing Atlassian invoice, and it needs no new supplier onboarding, no purchase order and no vendor security review of our payment handling. The documentation is public and needs no trial to read.

## Legal

- [Privacy policy](https://oktul.com/legal/privacy/index.md): What Oktul does with the information you give us, and with the licence detail Atlassian passes on.
- [Cookie notice](https://oktul.com/legal/cookies/index.md): One cookie is set without asking, and it holds your answer. Analytics and the support widget both wait to be asked.
- [Website terms](https://oktul.com/legal/terms/index.md): The terms on which oktul.com is made available, and what you may do with what is on it.
- [Application licence](https://oktul.com/legal/app-terms/index.md): The end user licence agreement (EULA) for Oktul applications installed from the Atlassian Marketplace.
- [Data processing addendum](https://oktul.com/legal/dpa/index.md): The Article 28 processor terms for Oktul applications, published rather than sent on request.

## Languages

- English: https://oktul.com/
- Estonian: https://oktul.com/et/

Documentation is English only. Marketing pages exist in both languages as peers,
and the Estonian translation is machine-drafted pending review by a native speaker.

## Everything in one file

- https://oktul.com/llms-full.txt