About Vi
Vi is project management and helpdesk for software teams. Customer requests come in, finished work goes out, and everyone stays in the loop.
Why does Vi exist?
Vi exists because in most software teams the customer, the manager and the developer each see a different version of the same work.
Requests come in by email. Someone copies them into a tracker. Developers stop coding to update ticket statuses. Customers keep writing "any update?" because nobody tells them anything. I built Vi so that one request has one path, from the customer's email to the developer's IDE and back to the customer, without anyone retyping it along the way.
Who is behind Vi?
Over more than 30 years as a software developer, hardware designer and, at times, software team lead, I kept running into the same gaps in how software is built and managed. Vi is my attempt to build the tool I often wished I had on real projects.
Before Vi, I built many systems for myself and for clients. Among them:
- a task management system
- an access control system installed in several refineries and banks
- an attendance and time-tracking system with more than 30,000 customers, small and large, supported by a team of just three people
- a sports club membership management system
- more than 30 other software products
I designed and built each of them from the ground up, and each one taught me something new about building, maintaining and managing software.
When you write to support or ask for a feature, the person who answers is the person who builds the product.
Vi is young, but it has more than 30 years of experience behind it.
Who advises Vi?
Practitioners who help shape Vi and advise the teams that use it.
Sajjaad Ramzey
ITSM & Project Delivery Advisor
PMP, ITIL v4 | 15+ years in IT service delivery and project management
Reviews Vi from the ITSM and project delivery side, and advises Vi customers on setting up their service and delivery processes: workflows, SLAs and the handoffs between support and development.
What do we believe?
Every task has one owner.
Vi gives each task a single assignee, on purpose. Shared ownership usually means nobody owns it.
Status should come from the work, not from manual updates.
When developers finish their step with Commit & Close, the task moves to the next step and the next person.
Customers shouldn't have to ask.
They get a status link and an automatic email when their request is done.
Your source code stays on your machine.
Vi links tasks to commits. It does not host or read your repository.
How Vi handles securityWe say what Vi doesn't do.
Vi has no mobile app yet and no automated import from Jira. If Jira or Linear fits your team better, our comparison pages say so.
Vi vs JiraWhere is Vi today?
- Plans: Free, Pro and Business. Current prices are introductory and apply until the end of 2027.
- IDE integrations: VS Code, Visual Studio, RAD Studio and Lazarus are available. JetBrains is planned.
- The site and app are available in English, Persian, Turkish and Spanish.
- Want to try Vi with a real team? Run a pilot with one team first.
How can you reach us?
Through the contact form, or on the profiles below.
See Vi with your own team
Start free, or write to the founder directly.