Focused software for Atlassian teams.

Eriksen Labs builds apps for Atlassian Cloud and tooling for people who work with AI models.

The Mermaid Diagrams & Gantt editor in Confluence's dark theme: flowchart source on the left, the rendered diagram on the right.

Mermaid Diagrams & Gantt for Confluence Write diagrams as text, see them render live.

Three apps. Two are on the Atlassian Marketplace, and the third is on its way there.

Mermaid Diagrams & Gantt for Confluence

Write diagrams as text, see them render live.

Flowcharts, sequence diagrams, ERDs, Gantt charts and mind maps written as plain text — with syntax highlighting, live preview, starter examples and one-click export.

Confluence Cloud Forge No scopes requested

Formerly Mermaid Studio for Confluence.

The editor with a Gantt chart: the release plan written as text on the left, the rendered timeline on the right.
The Request again dialog in the customer portal, set to repeat a request every 3 months, with the options Raise it now, Repeat on a schedule and Save as template.

Recurring Requests & Templates for Jira Service Management

Some requests come back every month.

Let the customer schedule them instead of raising them by hand, forgetting, or emailing an agent to do it.

Jira Service Management Forge Scheduling off until you enable it

Issue Templates & Create Defaults for Jira

Nobody has to remember the format.

When every bug report should answer the same questions, give each issue type a template, and Jira's own Create dialog fills it in.

Jira Cloud Forge Records nothing about who uses it

Documentation: Issue Templates & Create Defaults Coming to the Atlassian Marketplace
Jira's Create dialog for a bug, filled from the Bug report template, with the app's note on the Summary field: Filled from the Bug report template. Write your own, and it steps back.

None of this needs to be taken on trust.

Every app here is defined by what it deliberately cannot do, which is why its claims are checkable rather than promised.

A promise not to misuse your data is worth less than not being able to reach it. Each of these is visible to you without our cooperation.

Hosting
Atlassian Forge. We operate no servers and hold no infrastructure of our own.
Egress
None declared. Nothing is sent outside Atlassian, to us or to anyone else.
Permissions
Listed on each app's page or the security page, and on the install screen before you approve it.
Telemetry
None in the apps. This website measures page views and load times with Cloudflare Web Analytics, which sets no cookies. Details

Most apps ask you to send your data somewhere.

A typical Marketplace app runs on its vendor's own infrastructure. Installing it means your issues, your customer requests and your page content are copied to a company you have not met, on hosting you did not choose, alongside sub-processors you would have to read a policy to name. None of that is unusual. It is simply how most of the ecosystem is built, and it is why every install turns into a review.

The data that cannot leak is the data that was never sent anywhere.

So nothing is sent.

Everything here runs on Atlassian Forge. Atlassian hosts the code, the data stays inside the tenancy you already administer, and the app declares no egress — there is no address for your content to travel to, including ours. That is not a policy we could quietly change. It is a property of where the software runs.

Recurring Requests' manifest.yml, read by Atlassian before the app runs
read:servicedesk-request
Read the request the customer chose to repeat
write:servicedesk-request
Create the repeat, attributed to that customer
read:jira-work
Read the answers of an attached form
storage:app
Hold schedules, templates and settings, in storage Atlassian operates
report:personal-data
Report the account ids it stores each week, so data for closed accounts can be erased
External permissions
None declared No fetch, no images, no scripts, no addresses of any kind. Forge blocks any outbound call an app has not declared, and this app declares none — so there is nowhere for your content to go, including to us.

Security, privacy and the DPA

From the lab

Lab

Research

We scanned 323 Next.js apps. In 21 of them, something deletes data without checking who is asking.

Sixty per cent of what we found was not in an API route at all. It was in server actions — files whose names promise a library and deliver a public endpoint.

Read the study

The study's figure: one cell per repository scanned, 323 in all; 147 marked as able to delete, charge or change access; 21 of those flagged with no visible check.