Viktor charges workspace credits not seats

Credit based pricing turns Viktor into a usage utility, not another software seat line item. That matters because the product does work on behalf of a whole team, across chat, scheduled tasks, and hosted Spaces, so value scales with how much work gets delegated, not with how many employees are invited. A shared pool also makes adoption easier, because a manager can add more people without triggering a new license purchase each time.1 2 3 4

• Viktor sells one monthly credit pool per workspace, with no per seat charge. Current public pricing is linear at $25 per 10,000 credits, and the 40,000 credit plan costs $100 per month. Unused credits roll over for one month, which makes the plan behave more like cloud usage than SaaS headcount pricing.1 4
• The credits are spent on concrete work, not on logins. Admins can see usage by conversation, scheduled task, teammate, and Space. That means a customer can tie spend to real outputs, like recurring automations, app deploys, or internal tools running on hosted infrastructure, instead of paying for mostly idle seats.2 3
• This model also matches how Viktor competes. Microsoft Copilot is licensed per user inside Microsoft apps, while Viktor is shared across a workspace, works across Teams, Slack, Microsoft 365, and thousands of other tools, and hands finished work back into chat. Shared credits fit that cross team, cross tool workflow better than named seats would.4

Over time, this pricing structure should push Viktor toward larger internal automation budgets. As more teams run scheduled jobs, build more Spaces, and route more recurring work through the product, spend can rise inside the same customer account without any packaging change, which is the cleanest path from team tool to broader operating layer.2 3 4