Foundation vs. Structure: Which Jira Portfolio App Is Right in 2026?

Foundation and Structure both give Jira Cloud teams cross-project hierarchical portfolios. Structure (14,071 installs, built on the older Connect framework) is the incumbent with a deep Expr formula engine. Foundation (Forge-native, free for 1–10 users, launched 2026) matches Structure's core capabilities — hierarchy, Gantt, Sync Agents — at a lower price point, with zero-egress data residency and one-click migration from Structure Cloud. Here's how to decide.

Which one is Forge-native?

Foundation is built entirely on Atlassian Forge. Structure is a Connect app — the older framework Atlassian is retiring. Since September 17, 2025, only Forge apps can be newly submitted to the Atlassian Marketplace, so every new PPM competitor entering the market is Forge-based by mandate. Existing Connect apps can keep shipping updates, but the platform direction is unambiguous: Forge is the future, Connect is maintenance mode.

For buyers this matters in three ways. First, data residency: Forge apps run inside Atlassian's cloud with zero egress by default, so Jira data never leaves Atlassian. Connect apps route data through the vendor's external servers. Second, IT review: Forge apps inherit Atlassian's own compliance posture, which shortens security reviews. Third, roadmap risk: Forge-native apps can adopt new Atlassian platform primitives (Rovo agents, Forge Realtime, Forge SQL) the moment they ship. Connect apps have to bolt them on externally.

How do their hierarchies compare?

Both apps give you unlimited-depth hierarchies that span any number of Jira projects and any issue types. You can put Stories under Initiatives under Epics under Themes — Jira's native six-level cap does not apply. Drag-and-drop reparenting, inline editing, and spreadsheet-like cell navigation work similarly in both.

The meaningful difference is the non-Jira node. Structure calls it a “folder” or “memo”; Foundation calls it a Flex Item. Flex Items exist only inside Foundation and are used for organizational grouping (program headers, portfolio buckets, temporary sort containers) without polluting Jira with non-issue records. Structure's folders do the same. Both tools allow these to have children that are real Jira issues, and both allow roll-ups across the synthetic parent.

Where Foundation pulls ahead: five density modes (from 44 px Comfortable down to 16 px Micro) let you fit 30+ rows on one screen for portfolio-level scanning. Structure has Compact mode but tops out at a less aggressive density.

How do their Sync Agents or formulas compare?

Foundation ships two Sync Agents today: JQL Insert pulls any JQL query into a parent node, and Child Extend follows Jira hierarchy (Epic to Story to Subtask) automatically. A third — Linked Items Extend, which follows Jira issue links — is on the near-term roadmap. Sync Agents run event-driven through Forge product events, so they refresh within seconds of a Jira change without costing API points.

Structure calls these “generators” and supports a larger catalog, including linked-issue generators, agile-board generators, and saved-filter generators. If you rely on generators beyond JQL + hierarchy today, Structure has more options.

Formulas are the bigger gap. Structure's Expr formula language has 100+ functions and is genuinely powerful — weighted roll-ups, custom-field arithmetic, conditional formatting rules written in code. Foundation does not have a formula engine in the MVP. It ships in Q1 2027 per the public roadmap. If you depend on Expr for portfolio reporting today, that is a real reason to stay on Structure until the engine lands.

Which has stronger Gantt and dependency tracking?

Both products treat the Gantt chart as a first-class view, not a bolted-on roadmap. Both support all four dependency types (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish), drag-to-link arrow drawing, critical-path highlighting, and baselines for planned-vs-actual comparison.

Foundation's Gantt has four zoom levels (Day, Week, Month, Quarter) and three scheduling modes per item — Auto (derived from children), Manual (pinned dates), and Locked (protected from roll-up changes). Dragging a bar edge resizes the underlying Jira due date. Dragging the bar itself reschedules it. Changes sync back to Jira within seconds through the inline-edit API, and the affected grid row animates to confirm the write.

Structure's Gantt (technically a separate extension called Tempo Gantt Charts) has been in market longer and handles very large plans well. It also supports resource allocation views that Foundation treats as a post-MVP feature. For pure planning timelines on 1,000 items or fewer, the two are close. For 5,000+ item plans with resource histograms, Structure is still ahead.

What does migration from Structure to Foundation look like?

Foundation ships a direct Structure Cloud importer. You generate a Structure API token in Tempo, paste it into Foundation's migration wizard, and pick the structures to import. Foundation reads each structure via the Structure Cloud REST API, rebuilds the hierarchy as a Lens, and maps generators to Sync Agents where the semantics match (JQL-based generators translate cleanly; Expr-driven generators flag as “review needed” since Foundation has no formula engine yet).

The wizard is non-destructive. Your Structure data stays untouched. Your Tempo subscription stays active. You run both tools side-by-side for as long as you want, validate the imported Lenses against the source structures, and cancel Structure when your team has fully moved.

For teams whose Structure investment depends heavily on Expr formulas, the honest answer is: import now to evaluate, but keep Structure running until Foundation's formula engine ships. See the full migration guide for step-by-step instructions and common gotchas.

How do pricing and free tiers compare?

Foundation is free for 1–10 users — no credit card, no trial clock, no feature gating on the free tier. Paid tiers start at a per-user price designed to undercut Structure at every bracket; exact pricing is published on the Foundation Marketplace listing.

Structure is also free for 1–10 users. Above that, pricing scales per user per month and varies by tier. Per Tempo's public Strategic Portfolio Management pages as of April 2026, Structure has raised prices three times in 18 months, with some tiers increasing more than 30%. That pattern — documented in Tempo customer forums and in analyst coverage — is a major reason teams are shopping for alternatives.

The durable pricing difference is strategic: Foundation is a new entrant with a mandate to take share, so our pricing stays below the incumbent. Structure is a maturity product inside a larger Tempo portfolio, so its pricing tracks upward with the rest of Tempo's catalog.

Which one handles Jira API rate limits better?

Atlassian enforced a new point-based Jira API rate limit on March 2, 2026: Tier 1 apps share a 65,000-points-per-hour global pool across every tenant. Fetching an issue costs 2 points. A JQL search returning 100 results costs 101 points. Apps that poll Jira on a timer can exhaust the global pool during a traffic spike and fail for everyone.

Structure, as a Connect app, historically uses polling to keep its structures fresh. Tempo has moved toward webhooks, but the Connect framework does not expose the same free event triggers Forge does. Every Structure refresh costs API points against the shared pool.

Foundation uses Forge product events — avi:jira:updated:issue, avi:jira:created:issue, avi:jira:deleted:issue — which fire for free and cost zero API points. When a Jira issue changes, Foundation's event handler updates the issue cache inside the installation and pushes a Realtime event to open Lenses. Foundation has also been granted Tier 2 rate limits (per-tenant, 100,000–500,000 points/hour), so heavy operations have more headroom than the Tier 1 global pool.

When should you stay on Structure?

There are three scenarios where Structure remains the better choice today. First, if you depend on Expr formulas for portfolio reports — weighted roll-ups, custom conditional columns, scripted aggregations — Structure's formula engine has no equivalent in Foundation until Q1 2027. Second, if your plans routinely exceed 5,000 items and rely on resource-allocation views; Structure's Gantt handles that scale today, Foundation optimizes for 1,000-item Lenses in the MVP.

Third, if your team depends on niche generators like board-based or saved-filter generators beyond JQL and hierarchy, Structure has more variety. Foundation's Sync Agent catalog expands each release, but is narrower today.

For everything else — cross-project hierarchy, Gantt with dependencies, inline editing, cross-project reporting, Cloud-only deployments, and teams priced out of Tempo's tiers — Foundation is the stronger fit, especially if zero-egress data residency and a lower price matter to your buyer.

Feature comparison

Frequently asked questions

Related

• Structure alternative for Jira — the demand-capture overview
• How to migrate from Structure to Foundation (step-by-step)
• Foundation security and data residency (Forge)
• Sync Agents: JQL Insert and Child Extend
• Foundation Gantt: dependencies, baselines, critical path

Sources

• Structure by Tempo — Atlassian Marketplace listing
• Adopting Forge from Connect — Atlassian Developer docs (Connect submissions closed September 17, 2025)
• Forge security model — Atlassian Developer docs
• Atlassian Cloud Fortified program
• Tempo Strategic Portfolio Management pricing