What is PVersion?
What PVersion does, its three parts (the console, the desktop app, the editor plugins) and the words these docs use.
PVersion brings version tracking, builds and publishing together in one place for game, film and software studios. Your team's files live on a server set aside for your studio; everyone works on the latest version, and every change that is submitted is recorded and versioned. Setting up, running and backing up the server is our job; you open your account and get to work.
What it does
- Built for big files. Only the files that changed travel back and forth, so even on projects of hundreds of gigabytes nobody waits.
- Nobody overwrites anybody. While someone works on a file that cannot be merged (a level, a model, a texture, a video project), the file is reserved for them and the others wait their turn.
- Everyone sees what they need to. Outside teams, freelancers and new hires work only in the parts you open to them.
- Everything is on record. Who changed what, and when, is in the history. If needed, you undo a change.
- Builds and publishing on their own. A submitted change can be built and published automatically; websites follow the same flow. See Builds and Web publishing.
- Your data stays in Türkiye. The servers are in Türkiye and every connection is encrypted. Backups run every night, and a second copy is kept for 14 days, also in Türkiye.
The three parts
| Part | Who uses it | What for |
|---|---|---|
| Web console | The studio owner and admins; everyone on the team can sign in | Account and plan, projects, team and permissions, backups, support |
| Desktop app | Everyone who works on the project | Downloading the project, getting the latest, submitting, browsing files and history |
| Editor plugins | People working in Unreal Engine or Blender | Doing the same without leaving the editor |
Web console
The console is the web page at https://console.pversion.com/. This is where you open your studio's account. Projects, team invitations, who can access what, your plan and payments, backups and support cases are all managed there. What each page is for is on Console overview.
Desktop app
It runs on Windows 10 and 11 and on Macs with Apple silicon or Intel processors. The Mac app works with Unity, Blender, Premiere Pro, After Effects, Photoshop and DaVinci Resolve projects. Unreal support and its plugin are Windows-only for now; if you use Unreal on a Mac, write to [email protected] and we'll build it on request. Everyone on the team installs it on their own computer and does almost all of their daily work in it: downloads the project, gets the team's work with Update and open, and sends their own work to the server with Submit. It shows your files with thumbnails, so you can see who has a file, its versions and its history. To install it, see Installing the app.
Editor plugins
The Unreal Engine plugin (Windows) and the Blender add-on bring getting the latest, submitting, file locks and history into the editor. The plugins never connect to a server by themselves; they talk to the PVersion app on the same computer, so the app must be installed. Unity needs no separate plugin: you get the latest and submit from the app. Details: Unreal Engine, Blender, Unity.
A working day
- In the morning, click Update and open in the app: the team's submitted work comes in, then the project opens in its editor.
- You work. The files you change are listed on the My changes page. A file someone else is working on shows a lock icon.
- When you are done, write one sentence about what you did and click Submit to server. The team gets your work the next time they update.
- For work that is not ready to submit, use Shelve: the work is stored on the server and is safe even if something happens to your computer.
These steps are covered in detail under Daily work: Getting the latest, Submitting, Locks, Shelving.
PVersion's words
These words always mean the same thing in these help pages and in the app:
| Word | Meaning |
|---|---|
| Studio | Your account in the console. Your projects, team and plan are gathered under this name; the console sometimes calls it the "organization". |
| Project | A game, a film or a piece of software. On the server it has its own files, history and permissions. |
| Server | The machine set aside for your studio where your projects live. We set it up, maintain it and back it up; you only connect to it. |
| Project folder | The copy of the project on your computer. On Windows the default is C:\PVersion\<project name>. |
| Getting the latest | Downloading what the team has submitted to your computer. |
| Submit | Sending one or more files to the server together with a description of what was done. Each submit is one line in the history. |
| Lock | A file that cannot be merged is reserved for the person working on it; nobody else can change it until they submit or discard it. |
| Shelve | Storing work on the server without sending it to the team. The team does not see it; you can pick it up from your other computer. |
| Workspace | The server's record of the copy on your computer: which folder, and which version of each file is there. The app sets it up for you. |
| Area | A folder inside a project (for example Content/Maps). Outside teams get permissions area by area. |
| Role | Your rights in the console: Owner, Admin or Developer. See Team and permissions. |
Where to start
For a new studio, the order is:
- Creating an account: register your studio and choose a plan.
- Installing the app: download the desktop app and connect it to the console.
- Your first project: create the project in the console and set it up on your computer with the app.
- Inviting your team: invite your teammates by email.
Ask the assistant on the site or write to [email protected].
PVersion