FAQ
Questions, answered from the code
Nothing on this page is a guess about how the product might behave. Each answer describes what the implementation does.
The product
- What is Vorkhurry?
- A multi-tenant work-management platform for teams that ship software. Projects, issues, boards, backlogs, sprints, a dependency-aware Gantt, initiatives above projects, documents, reports, and the organization structure and permissions to run all of it — with GitHub, Slack, Microsoft Teams, and Jira, Linear and CSV import connected.
- Who is Vorkhurry for?
- Software and product teams inside an organization that has more than one project and more than one kind of member. It is built around organizations, roles and permissions from the first screen, so it fits a company rather than a single team's list.
- What views does a project have?
- Overview, Board, Backlog, Sprints, List, Calendar, Gantt, Members and Settings. All nine are built; none is a placeholder.
- Is there a Gantt chart?
- Yes. Each project has a Gantt view built from issue start and due dates, with milestones, progress, and finish-to-start arrows drawn from the project's dependency edge set. Dependencies are checked for cycles.
Organizations and access
- How does organization management work?
- Every account belongs to an organization. There is no signup path that creates a user without one, and no way to reach the application without belonging to one. Inside it you have departments, teams, groups, members with roles, and projects those members are added to.
- How are permissions managed?
- There are 146 named permissions in a catalogue, grouped by area, with dangerous ones flagged. 20 role templates ship, from Owner through Engineering Manager and Developer to Guest and Viewer. Roles carry no hierarchy — a role is exactly the permissions granted to it. You can also override a single permission for a single member, and read the effective permissions for that person to see the result.
- Can one organization see another's data?
- No. Tenant scoping lives in one repository base class rather than in scattered query filters, PostgreSQL row-level security is a second independent backstop, and escaping either requires an explicitly named context manager that logs a warning. A cross-tenant read answers 404 rather than 403, because a 403 would confirm the row exists.
Integrations
- Does Vorkhurry support Git?
- GitHub, connected as a GitHub App scoped to the repositories you install it on. Issue keys in branch names, commit messages and pull-request text are matched to your projects and recorded as activity, and a pull-request event can move an issue to a status you have mapped. GitLab and Bitbucket are not implemented.
- Can I connect Slack?
- Yes — as an OAuth app with a bot token. You choose which event types the workspace receives and route them per project to a channel, with a default channel for the rest. Microsoft Teams is supported too, through an Incoming Webhook connector.
- Can I import from Jira or Linear?
- Yes, and from a CSV file. The import is a wizard: connect the source, preview the rows, map source statuses onto your workflow, validate, resolve conflicts row by row, then run it. Every source record is its own row with its own status, so the job is resumable and a re-run updates what it already created rather than duplicating it.
AI
- Does Vorkhurry support AI?
- There are eleven assist actions. On an issue: draft a description, suggest acceptance criteria, break it into subtasks, summarise the thread, suggest a priority. On a project: draft a delivery plan, propose milestones, identify risks. On a sprint: advise on scope, summarise progress, surface blockers.
- Who provides the AI API key?
- Your organization does. An administrator connects OpenAI, Anthropic or Google Gemini with your own account's key. There is no shared Vorkhurry key — the platform does not pay for or proxy anyone's model usage. The key is encrypted at rest and never returned by the API; responses carry a masked suffix only.
- Can we control what AI is allowed to do?
- Yes. AI is off until it is connected. You choose which models are enabled, set a default and per-feature overrides, and cap monthly spend. Every call is recorded as a usage row. Output arrives as a suggestion someone accepts or rejects — applying it to an issue is a separate, deliberate action.
Getting started
- What happens when I sign up?
- You create a workspace, not just a user. On a plan that requires no payment the workspace exists and you are signed in immediately. On a paid plan nothing is persisted until the payment provider's signed webhook confirms the payment — a forged success callback reaches no code that creates anything.
- How do people sign in?
- Email and password with Argon2id hashing, a single-use magic link, or Microsoft and GitHub OAuth where the deployment has configured them. Two-factor is TOTP with recovery codes. Sessions are device-bound and listable, and you can revoke one.
- Where does the pricing on this site come from?
- From the same plan catalogue the signup wizard reads — one public, unauthenticated endpoint on the Vorkhurry API. This site does not keep its own copy, so the price you see here and the price you are charged cannot disagree.
Start with your team, not with a sales call
Create a workspace, invite the people you work with, and bring your existing issues in from Jira, Linear or a CSV.