Trust center

Hooq Architecture Diagram

Last updated:

App: Hooq, work item sync for Jira Cloud (Atlassian Forge). Vendor: Limbus Lab.

Hooq synchronizes Jira work items between two Jira Cloud sites that administrators deliberately connect, or within one site. Hooq runs entirely on the Atlassian Forge platform. Hooq does not operate any server, database or storage of its own: no customer data is processed or stored outside Atlassian infrastructure by Hooq.

Architecture diagram

Hooq architecture: data flow between two Jira Cloud sites on Atlassian ForgeTwo Jira Cloud sites, A and B, both inside Atlassian infrastructure. In each site, Jira work items and events connect to Hooq Forge functions, a Hooq web trigger and Forge Events queues. The functions read and write Forge hosted storage for that site installation, and talk to the Hooq pages (admin pages, issue panel, gadget) through the Forge bridge. Between the two sites, Hooq functions send HTTPS POST requests, signed with HMAC and carrying a timestamp and a nonce, to the web trigger of the partner site, in both directions. There is no server, database or storage operated by Hooq outside Atlassian infrastructure.Jira Cloud site AAtlassian infrastructureJira work items and eventsHooq Forge functions,web trigger and Forge Events queuesForge hosted storage(site A installation)Hooq pages:admin, issue panel,gadgetJira events in;Jira REST API outread, writeForge bridgeJira Cloud site BAtlassian infrastructureJira work items and eventsHooq Forge functions,web trigger and Forge Events queuesForge hosted storage(site B installation)Hooq pages:admin, issue panel,gadgetJira events in;Jira REST API outread, writeForge bridgeHTTPS POST,HMAC-signed,timestamp and nonceA to BB to Ato the partner'sHooq web triggerNo Hooq-operated server, database or storage outside Atlassian infrastructure
Figure 1. Hooq between two Jira Cloud sites. A text description of the diagram follows below.

In a same-instance Hooq both ends are the same site: the Forge functions read one project and write another through the Jira REST API, and no web trigger call is needed.

Data flow

  1. A work item changes on site A. Jira raises a product event that invokes Hooq’s Forge function on site A.
  2. Hooq reads the item through the Jira REST API with the permissions the administrator approved at install, and reads its own configuration (mappings, settings, links) from Forge storage.
  3. Hooq builds a message containing the fields the administrators chose to sync, signs it (HMAC-SHA-256) with the secret shared by the two paired sites, adds a timestamp and a one-time nonce, and POSTs it over HTTPS to the partner site’s Hooq web trigger, which is a Forge-hosted endpoint on an Atlassian domain.
  4. On site B, Hooq verifies the signature, the timestamp (five-minute window) and the nonce (replays are rejected), places the message on a Forge Events queue, and a Forge function writes the result to Jira through the Jira REST API.
  5. Forge Events queues hold messages briefly between steps. They are Forge platform services.

What crosses between paired sites: only what the administrators configured to sync (for example summary, description, status, comments, attachments, worklogs and mapped custom fields), plus identifiers needed for linking (issue keys, project identifiers, sync identifiers) and user display names where they appear in synced content. Data goes only to the partner that the administrators of both sites approved.

Network diagram

Network connections used by Hooq
FromToProtocolAuthenticationNotes
User’s browserJira (Atlassian) and the Hooq pages inside JiraHTTPSAtlassian user sessionHooq pages are rendered by Forge inside Jira
Hooq Forge functionJira Cloud REST API of the same siteHTTPS, via Forge’s managed clientForge-managed OAuth 2.0 app token, scopes in the Marketplace listingNo credentials held by Hooq
Hooq Forge function (site A)Hooq web trigger (site B), an Atlassian-hosted Forge URLHTTPSHMAC signature, timestamp, nonce, paired connector identityOnly network call to an address Hooq stores; outbound access is limited by the Forge egress allow-list in the app manifest
Hooq Forge functionForge hosted storage and Forge EventsAtlassian internal, Forge-managedForgePer-installation scope

Hooq makes no connection to any non-Atlassian host. There is no Hooq-operated server, load balancer, database, queue, analytics service or third-party API in the architecture.

Declared outbound (egress) domains in the app manifest are all Atlassian domains. The list is in Subprocessors and Third-Party Integrations.

Where data is stored

Only in Forge hosted storage (key-value) provisioned per site installation, plus Jira itself. See Encryption at Rest and Data Retention and Deletion.

Hooq overview · Trust center · Questions: [email protected]