Skip to content
LayaHelp Centre
laya.netOpen app
GuidesIntegrationsTroubleshootingContactlaya.netOpen app

Laya WorkflowOS Architecture Diagram and Data Flow

How Laya WorkflowOS is connected: where it runs, the data that moves, where it is kept and how it is protected, with a diagram to file with your security review.

Last updated

Print-optimised: choose “Save as PDF” in the dialogue
On this page

What this covers: Laya WorkflowOS on the Atlassian Marketplace (Laya WorkflowOS), as it works in its current release: where it runs, the data that moves and where it is kept. It is made by LayaNet LTD (company number 17430595), a company registered in England and Wales. On the Atlassian Marketplace it uses the vendor name Agile Pulse.

Last reviewed: 20 October 2026.

Architecture and data flow diagram

Laya WorkflowOS Architecture Diagram and Data FlowHow Laya WorkflowOS is connected: people use it inside their Atlassian site, where it runs on Atlassian Forge. It sends nothing outside Atlassian. The numbered list under the diagram says what each arrow carries.Inside yourAtlassian sitePeople in yourJira siteSigned in withtheir AtlassianaccountLayaWorkflowOSAn AtlassianForge appKeeps data inForge storageJiraYour issuesForge LLMsAtlassian’s AIservice, insideAtlassian123Laya WorkflowOS Architecture Diagram and Data FlowHow Laya WorkflowOS is connected: people use it inside their Atlassian site, where it runs on Atlassian Forge. It sends nothing outside Atlassian. The numbered list under the diagram says what each arrow carries.Inside your Atlassian sitePeople in your Jira siteSigned in with their Atlassian accountLaya WorkflowOSAn Atlassian Forge appKeeps data in Forge storageJiraYour issuesForge LLMsAtlassian’s AI service, inside Atlassian123
Used whenever the app is usedDashed: only in the cases its words giveNumber: the same number in the list below says what the arrow carriesShaded area: a boundary, named on it

In words

  1. People use Laya WorkflowOS inside Jira, signed in with their Atlassian account.
  2. Laya WorkflowOS reads from Jira as it works. In Jira: whatever your rules do, such as field changes, comments, transitions and new issues, made by the app. Emails a rule sends go through Jira’s own notifications.
  3. Optional: only when someone uses an AI feature, or a report with AI summary ticked is made, and AI assist is on for the site: the app sends Forge LLMs, Atlassian’s AI service, only the fields listed under How AI is used. Nothing is sent outside Atlassian for AI. Requests are processed inside Atlassian’s platform, under Atlassian’s terms for Forge apps. The app keeps an AI answer only where it is saved: in a rule someone saves, in a report file for 24 hours, or in the conflict scan results for 24 hours.

The app connects to nothing outside Atlassian: its Forge permissions allow no outside address.

What is kept, where, and how it is protected

Laya WorkflowOS: the data kept, where, and how it is protected
DataWhere it is keptHow it is protected
Forge storage: automation rules (with the account id of the person who made each) and their last 20 versions, run logs (rule, issue key, trigger, result and errors), an audit log of changes (with who made them), settings, saved searches, schedules, AI usage counts, export and report jobs, and export files (kept for 24 hours).Inside your Atlassian site: Forge storageThe app makes no connections outside Atlassian: its data moves and is stored only inside Atlassian’s cloud, under Atlassian’s own security controls. Atlassian describes them in its Trust Center.
Jira itself: whatever your rules do, such as field changes, comments, transitions and new issues, made by the app. Emails a rule sends go through Jira’s own notifications.Inside your Atlassian site: JiraThe app makes no connections outside Atlassian: its data moves and is stored only inside Atlassian’s cloud, under Atlassian’s own security controls. Atlassian describes them in its Trust Center.

Never kept: Anything outside Atlassian: we run no servers for this app.

Retention and deletion

  • Uninstall: The app deletes all the data it stored.
  • Deletion: Export files are deleted after 24 hours. Rules, logs and the audit log stay, within their size limits, until you delete them or uninstall the app. A Jira admin can also erase all of the app’s data.
  • Atlassian’s personal data reporting: The app does not use Atlassian’s personal data reporting yet; rules keep their owner’s Atlassian account id.
  • Logs: The app’s run logs stay in Forge storage, inside Atlassian.

Sub-processors

Sub-processors that may process Laya WorkflowOS data
Sub-processorPurposeLocation
AtlassianRuns the app, its storage, Jira’s notification emails and its AI features (Forge LLMs).Where your Atlassian site is hosted

About this document

  • This document is drawn from the same records as the Laya WorkflowOS trust page, and changes when they change.
  • Detailed network information is not published, to protect the service.
  • Questionnaire references: CAIQ v4 DSP-05 (data flow documentation) and DSP-19 (data location). These are references for your review, not a compliance claim.
  • Security contact: support@laya.net, with "Security report" in the subject line. Please never include passwords or tokens.
Laya WorkflowOS Architecture Diagram and Data Flow: change history
DateChange
20 October 2026First published.
Still stuck?

Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.

Contact support