Early-access pricing. Feature availability, usage allowances and onboarding scope will be confirmed in your proposal before subscription.
Pricing questions.
How plans, workspaces and onboarding work. If something isn't covered here, ask us on your demo call.
01What is a product workspace?
One product's delivery setup in Pyloq: its ticket tracker project, repositories, Slack or Teams channel, releases and the people working on it.
02Is pricing per user?
No. You pay per product workspace, not per seat. Each plan includes up to a set number of users (10 on Starter, 25 on Pro, 50 on Growth, unlimited on Enterprise), so a growing team moves up a plan rather than paying for every new person.
03Which tools does Pyloq work with?
Jira or ClickUp for tickets, GitHub for code, and Slack or Microsoft Teams for your team. Each workspace uses one ticket tracker.
04Does Pyloq replace our existing tools?
No. Your tickets stay in Jira or ClickUp and your code stays in GitHub. Pyloq connects them and does the follow-up work between them.
05Does a completed ticket mean a feature has shipped?
Not necessarily, and Pyloq keeps the two apart. It shows a change as merged, released or deployed based on what GitHub reports, and says so when that evidence is missing.
06Can Pyloq work with AI assistants?
Yes. Connect Claude Code, Cursor, Codex or another MCP-compatible tool to ask about tickets, standups and releases. Pyloq gives the tool your team's rules for branches, PR titles, commits and tests with every ticket, and can keep them in each repo's AGENTS.md. Requirements sent from an AI tool arrive in Pyloq as drafts for your review, and tickets only move when you ask.
07How do we get started?
Book a demo. We'll look at your workflow, confirm which tools to connect, and agree the onboarding scope before anything is connected.