Getting Started

Last updated: July 2026

One account, every product

Javer uses a single sign-in called Javer ID. One email and password gets you into Web Hosting, Simple Hosting, and Game Hosting — you do not create a separate account for each. Sign in to one and you are already signed in to the others.

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

Sign up from any product's login page. You will be asked for an email address and a password of at least 10 characters.

You must verify your email before you can sign in. Check your inbox for the verification link — it is valid for 24 hours. If it does not arrive within a few minutes, check spam, then use the resend link on the login page. Accounts that sign up with Google are already verified and skip this step.

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 containers or full Linux VMs, add managed Postgres or MySQL, connect custom domains, use the API. Start here if you are comfortable with the words "container" and "environment variable".
• 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

Email ask the support assistant or email [email protected]. 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.