More participants should improve the estimate, not the invoice.
Only the organizer pays
Voters and spectators participate for free, so the right people can join without another seat calculation.
Why Pokor exists
Estimation should uncover uncertainty.
Not create more admin work.
Pokor keeps the backlog connected, lets every useful voice join for free, and turns a spread of estimates into a conversation the team can act on.
The problem
The work already has a home. The planning room should respect it.
The first minutes of refinement are often lost copying issue titles, reopening links, and explaining which version of a story is current.
Pokor brings selected work into the room, keeps its source context attached, and can return finalized estimates to supported Jira, Notion, and GitHub workflows when the organizer enables write-back.
Product decisions
Built around the friction teams actually feel
These are not slogans added after the product. They are constraints we use when deciding what Pokor should do next.
Copying work between tools creates stale context.
Keep the source of truth connected
Import selected backlog items and return final estimates to supported sources only when the organizer configures that workflow.
A wide vote is useful only when the team understands why.
Make disagreement actionable
Private voting, rationale, confidence, re-votes, and retrospectives help the team expose assumptions instead of averaging them away.
Standing teams should not rebuild the room every week.
Reuse the setup
Teams, saved decks, templates, async windows, and shared AI credits keep recurring planning work ready for the next session.
How Pokor operates
The practical trust questions, answered plainly
Security and privacy claims should be specific enough to verify. The detailed controls live in the security overview and trust center.
EU-hosted infrastructure
Pokor application infrastructure and primary data stores run in the European Union.
No Pokor password database
Authentication uses one-time email codes or supported identity providers. Integration tokens are encrypted at rest.
Stripe handles payment details
Card numbers and CVCs do not pass through Pokor servers. Pokor stores billing identifiers and subscription state.
Guest participation can be removed
Guests use a random token. Signing out removes the guest cookie and deletes participation data associated with that token.
Scoped, explicit integration actions
Pokor imports the items you choose. Finalized values leave Pokor only through a write-back mode the organizer explicitly configures.
Built in public
If Pokor adds friction, tell us where.
The public changelog records meaningful product changes. Bugs, feature ideas, and awkward workflows belong on the contact page.