New SprintPoker now comes with every account

One board for all your work.

Run your team's board in Laya, or mirror Jira and the other tools you already use. Turn an idea into a plan with Build, then hand the cards to AI agents.

No cap on members or boards, on any plan. Free plan, no card needed: see plans and pricing

A Laya board in the picture shows each way in at work: PAY-203 moved to In progress. WEB-88 synced from Jira, both ways. Build turned your idea into a plan of cards. PAY-231 estimated at 5 in SprintPoker. Claude Code opened a draft pull request. Shared by link. Viewers need no seat.

NewLaya Build: from an idea to a product you can see

What do you want to build?

Describe it in a sentence. Laya reads it back and lays out the plan before you sign up, then draws clickable screens once you are in. You choose who builds it: your own AI agent, or Laya's.

No account needed to see the plan.

Laya plans it. You choose who builds it: your own agent

orLaya Agent
  1. 01UnderstoodLaya reads your idea back.
  2. 02ConceptClickable screens, once you sign in.
  3. 03PlanPhases you approve first.
  4. 04ProjectBuilt in your own repository.
Included With every Laya.net account

Your Laya.net account comes with SprintPoker.

Planning poker for your team, from the team behind SprintPoker for Jira and Azure DevOps. Estimate a Laya board or Jira issues together. Guests join with just a name.

  • SprintPoker by Laya Included

    Live or async rounds. Votes stay hidden until the reveal, and the agreed estimate can be saved straight to the Laya card or Jira issue.

  • SprintRetro Coming soon

    Retrospectives with ready-made templates, anonymous cards and votes. Available today for Jira and Azure DevOps.

Free on Laya’s free plan, with the same core limits as SprintPoker for Jira. Team and Business plans remove those limits and include every Agile Pulse app on Laya.net (SprintPoker, and SprintRetro when it launches).

App: its own Marketplace app, from the same team. Soon: coming to Laya.net.
AppLaya.netJiraAzure DevOps
SprintPokerIncludedAppApp
SprintRetroSoonAppApp
The Laya layer

Every board. One live surface.

Each team stays in the tracker it already uses. Laya streams them all into one customizable board: no exports, no cutover, no retraining. Each card keeps its source badge, so you always know where the work really lives. Explore every integration to see how each connection works.

Hover a provider to isolate its cards. Each landed card carries its source badge.

Mirror · Speed · Sync

Mirror any board on a faster, more beautiful surface.

Point Laya at Jira, Azure DevOps, Monday, GitHub, or GitLab and get a like-for-like board (every column and card exactly where it belongs) rendered on Laya's UI from a synced mirror we keep current and delete when you remove the board. Same board, our surface: smoother, more reactive, quicker to the touch than the native tool. Rather build your own? Native Laya boards embed external boards with full two-way sync.

Jira · native
To Do
In Progress
Done
renderfull re-fetch
Laya · mirrorlive
To Do
In Progress
Done
renderinstant · cached

Like-for-like

Every column, card, and field lands exactly where it does in the source. Nothing to relearn, just a nicer place to work.

Faster & reactive

Rendered from a synced mirror on Laya's own engine, snappier and smoother than the board it mirrors.

Native + two-way sync

Prefer your own? Build a native Laya board and embed external boards inside it. Edits flow both ways, in real time.

In practice

Three agencies, three trackers, one project.

A client had several third-party agencies delivering the same project, each working in its own board, in its own tool, none of them connected. With Laya they collaborate on one shared board in real time, while every agency's work stays owned on its own system of record.

  • Everyone in sync: one live board across all the agencies
  • Nobody gives up ownership: each board stays its own source of truth
  • Clear data lines: each agency's tool stays its system of record; Laya mirrors only the boards they choose to share
Show your work outward

The people who need to see it rarely have a seat

Clients, executives, partners and half the business will never have a Jira, Azure DevOps, monday.com, GitHub or GitLab seat, and nobody is buying one just so they can watch progress. Share a live board instead, and when they need to do more than watch, 2-way sync lets them join in.

  1. Share a linkAny board, read-only, revocable
  2. They unlock itOptional password on mirrored boards
  3. They see it liveNo seat in your tracker, nothing installed
  4. They join inA free Laya account lets them edit and comment, and 2-way sync carries it back to your tools

A link, not an invitation

Share any board read-only. Viewers open it in a browser and see live progress. No seat in your tracker, no Laya account, no "request access" email. Revoke it the moment an engagement ends.

Locked down if you want

Links are view-only, and nobody needs an account to open one. Turn a link off at any time. For boards mirrored from a connected tool, you can also put a password on the link.

Every source, same link

Boards mirrored from any connected tool share the same way, including a master board that spans several of them at once.

When watching isn't enough

Give them a free Laya account and the board becomes hands-on: they move cards, edit items and add comments, and 2-way sync carries every change back to the source tool under your workspace's connected identity.

Works for everything you connect: share a Jira board with clients without a licence, share an Azure DevOps board externally, or send a live monday.com, GitHub or GitLab board to people outside your organisation.

The cost of fragmentation

Your org doesn't have one project tool. It has a pile of them.

Engineering plans sprints in one tracker. A platform team lives in another. Ops and marketing run a third. Status rolls up by hand into spreadsheets, and nobody trusts the result.

There are two costs. Your people pay the first: knowledge workers toggle between apps ~1,200 times a day, and it takes nearly 10 minutes to re-enter flow after each switch. The average employee now spends 60% of their time on "work about work": chasing updates, sitting in status meetings, hunting for information.

Leadership pays the second: when every team sits in its own tool, there's no single source of truth. Executives rarely trust reports stitched together from patchwork dashboards, and disconnected ecosystems are tied to a 40% higher chance of missing cost, scope, or schedule targets.

~1,200×
app toggles per knowledge worker, per day
HBR · Qatalog / Cornell
60%
of the workday spent on "work about work"
Asana Anatomy of Work
+40%
higher chance of missing cost / scope / schedule targets
Gartner, via Celoxis
The instinct is to standardize everyone onto one tool. But rip-and-replace is exactly where adoption dies. The fix isn't moving the work. It's overlaying it.
THE SYSTEM

Five pillars. One layer over all your work.

Click through the system: each pillar is a live, shipped capability.

PILLAR 1.0

One layer over every board.

See and run all the boards your teams already use, side by side in one place. They keep their tools and habits; you get one view to see and steer it all. Connect the big two via OAuth and the rest with a secure API token.

Every source integrates deeply, with the same fields and two-way sync across all five. Jira and Azure DevOps connect in one click via OAuth for the fastest live sync; Monday, GitHub and GitLab connect with a secure API token.
To Do
Auth rate-limit spike
JIRA
Sync webhook retries
GITLAB
In Progress
Pipeline cache warm-up
ADO
Q3 launch checklist
MONDAY
Done
Release v2.4 tag
GITHUB
MAKE IT YOURS

Board Studio, live. Drag a card to Done.

Re-skin the board with one click, pick the column effect, and drop a card into Done to fire the celebration. Customization as control: you own the surface, not the vendor.

See it, don't take our word

Watch an edit travel both ways, live.

Drag a card in the Laya pane. Watch it mirror into Jira instantly. Move it on the Jira side, and Laya catches up. Two tools, one truth, in both directions.

Trust by design

Data minimization, by design.

For the boards you connect, your provider stays the system of record. We store a mirror of what we need to render and sync those boards, and we delete it when you remove the board. For boards you build natively in Laya, that data lives with us as your system of record: encrypted at rest, and yours to export anytime. Either way, we connect with scoped credentials, encrypt provider credentials at rest and all traffic in transit, act only on your instruction, and never repurpose your data or use it to train models.

Remove a mirrored board and our copy goes with it. The original stays with your provider. Native boards are yours to export before you go.

Read more about security at Laya

True today
  • Encryption in transit on all traffic
  • Provider credentials encrypted at rest (AES-256-GCM)
  • We act on your instruction, with no repurposing of your content
  • Mirrored data deleted when you remove a board · native data encrypted at rest · never model-trained
Compliance & assurance

Every claim above links to the document behind it in the Trust Centre.

One board for every tool.
No migration required.

Connect Jira, Azure DevOps, Monday, GitHub, and GitLab. Give leadership one live view today.

Connect your first board in minutes. Free plan, no card needed: see plans and pricing