Getting Started

Last updated: August 2026

One account, every product

Javer uses a single sign-in called your Javer Account, at id.javer.pro. One email and password gets you into Web Hosting, Simple Hosting and Game Hosting — as long as you use the Continue with Javer Account button on each one.

One account does not mean one plan or one bill. Each product keeps its own plan and its own billing. Paying for Simple Hosting does not change what you get on Game Hosting.

Signing out is per-product, though. Logging out of Web Hosting does not sign you out of Game Hosting, the same way signing out of one Google product leaves the rest alone.

Creating your account

You create one Javer account, at id.javer.pro. Every product's login page sends you there. Press Continue with Javer Account, then choose New here? Create a Javer account. You need an email address and a password of at least 10 characters. Continue with Google works instead, if you prefer.

Web Hosting also still has its own email and password form. An account made that way works on Web Hosting only — it will not sign you in to Simple Hosting or Game Hosting.

There is no verification email to wait for. Your account is created and signed in straight away. Javer only emails you for sign-in codes and password resets — so if you are sitting waiting for a link, you are not stuck, you are already in.

Which product do I want?

The three products solve different problems. Picking the right one first saves a lot of time:

• Web Hosting — you want control. Choose memory and CPU, run apps or full Linux VMs, add managed Postgres or MySQL, connect custom domains, use the API. Start here if you are comfortable choosing how much memory and CPU something gets, and setting environment variables.
• Simple Hosting — you want your site online without decisions. No server specs to pick, no sizing, no infrastructure vocabulary. Connect a repo or drop a zip and it deploys.
• Game Hosting — Minecraft servers, with version and mod-loader selection, an in-browser console, and one-click mod installs.

You can use all three with the same account, and nothing stops you moving between them later.

Your first deploy

On Web Hosting, from your dashboard:

• Click Deploy App and choose your source — a connected GitHub repo, a public Git URL, or a zip upload.
• Give it a name. This becomes your address, so myapp gives you myapp.javer.pro. Lowercase letters, numbers, and dashes, 3–32 characters.
• Pick memory and CPU, or leave the defaults. You can change these later.
• Click deploy and wait. A static site is live in seconds. A Node app with dependencies takes longer while they install — keep the tab open until the URL appears.

If your app runs a server rather than serving static files, it must listen on the PORT environment variable that Javer provides. Hardcoding a port number is the most common cause of a deploy that appears to work but returns 502. The Web Hosting guide covers this in detail.

Getting help

The quickest route is the Support tab in your panel — the assistant there can already see your plan and your apps, so you do not have to explain your setup. If it cannot solve something it opens a ticket with a case number and a human replies on that ticket. Not logged in? Use javer.pro/support, and if you are locked out of your account entirely you can pull up an existing ticket there with your case number and the email you used. You can still email support@javer.pro if you prefer. Javer is run by a small team, so you are talking to someone who can actually change the thing you are asking about. Include your app name and roughly when the problem started.

Live service status for every product is at javer.pro/status.