The complete guide · 7 min read
Cyberpunk OPEN//77 Server Hosting: The Complete Guide
How the platform is put together, what the Open Alpha means in practice, how a server gets licensed and listed, how resources work, and how to run a community server without losing a weekend to an update. Every platform fact comes from the official OPEN//77 documentation.
By Matthew Griffin, Owner, Gaming DeluxePublished · Updated
In this guide
- How OPEN//77 Is Put Together
- What Open Alpha Means for Your Community
- License Keys and Getting Listed
- server.jsonc, Ports and Startup Options
- Resources, Game Modes and Data
- Moderation, Warden and Updates
- What to Compare Before You Rent an OPEN//77 Server
- OPEN//77 Server Glossary
- OPEN//77 Server Help and Official Links
How OPEN//77 Is Put Together
Cyberpunk 2077 is a single-player game. OPEN//77 adds a multiplayer layer on top of it, and the official docs are careful about what that layer is. It is not one official server, not a fixed game mode and not a peer-to-peer co-op mod. It is the infrastructure that lets anyone run a Cyberpunk 2077 server, a client that finds those servers and connects to them, and a toolkit for building game modes. The docs put it in one line: if you know how FiveM works for GTA V, that is the shape.
- The launcher and client: players sign in, the launcher checks their game and installs the multiplayer update. The client runs alongside the game and is designed to leave single-player saves and mods alone.
- Dedicated servers: each one owns the shared world and accepts player connections. The server is authoritative: it decides positions, inventories, vehicles, loot, time and weather.
- The master: the OPEN//77 service that checks license keys and keeps the public server directory.
- Resources: Lua packages that hold all the gameplay.
Because nothing is peer to peer, a world exists only while its server runs. That is the whole case for hosting: a server in a data centre keeps economies, factions and stories going while every member of staff is asleep.
What Open Alpha Means for Your Community
Open Alpha is open in the literal sense. Launcher and server downloads are public, and the docs state that no access application, invitation or staff approval is needed. You do not even have to join the Discord first. It is also an Alpha in the literal sense, and the official guide lists what to expect.
- APIs, network protocols and resource formats may change, so back up configuration, persistent data and custom resources before updating.
- Each system has documented limitations, for example which models, bodies and animations are supported.
- Repeated reconnects can leave a stuck animation or camera; the advice is to restart the game and report the steps.
- Launcher, client and server have separate version numbers, and you should use compatible releases from the official downloads.
Be straight with your players about this. A community that knows it is testing an Alpha forgives a rollback; a community that was promised a finished game does not. The public roadmap talks about priorities, in order: reliability and developer feedback, then compatibility and capacity, then the wider ecosystem. It gives no release dates.
License Keys and Getting Listed
Every server on the platform belongs to an account. Anonymous servers are not part of OPEN//77: without a license key a server cannot enrol and is never listed. The key is free, and the process is short.
- Register on open2077.net and verify your email address.
- Open Server license keys in your account and create a key. Give it a label so you can tell your servers apart.
- Copy the key at once. It is shown only once; the platform stores just a fingerprint and cannot show it again.
- Give the key to the server, either through the OP77_LICENSE_KEY environment variable or the masterServer.licenseKey field in server.jsonc.
- Set identity.name and identity.visibility, check that network.publicEndpoint is your public IP and port, and start the server.
On start the server presents the key to the master, receives a short-lived run lease that is renewed with every heartbeat, and publishes its name, endpoint and player count. There is no listing form to fill in: the config is the listing. A public server then shows up in the launcher and on the website. Stop the server or revoke the key and it drops off again.
server.jsonc, Ports and Startup Options
The server reads its settings from server.jsonc, a JSON file that allows // comments. A handful of fields matter on day one.
| Setting | What it does |
|---|---|
| identity.name | The name players see in the launcher and the server list |
| identity.visibility | public to be listed, private to stay enrolled but hidden |
| network.publicEndpoint | The address handed to players: a public IP or hostname plus the port |
| network.maximumPlayers | The player limit of the server |
| masterServer.enabled | Leave it true so the server enrols and is listed |
By default the game uses UDP port 11778 and players download resources over TCP port 11779. Both must be reachable from the internet, because a player who cannot fetch your resources cannot enter the world. On a hosted server the ports are assigned for you, so use the ones your panel shows.
Any config field can also be set when the server starts, with options such as --max-players or --log-level, or with OP77_CONFIG environment variables. The log level is worth knowing: info is the default, and debug shows much more when you are chasing a problem. Switch back afterwards, since detailed logging on a busy server produces a lot of output.
Resources, Game Modes and Data
The OPEN//77 site says it plainly: gameplay on a server is not configured, it is scripted. A resource is a folder with a manifest file called open77.lua, server scripts, client scripts and, if you want an interface, WebUI pages. The manifest names the scripts and declares permissions, so a resource only gets the parts of the game it asks for. Each resource runs in its own isolated Lua environment.
The resources folder is grouped by category: system for the official platform resources such as chat and voice, gamemodes for playable modes such as freeroam, and assets for maps, vehicles and other packages. The server download already contains Freeroam, so a new server has something to play before you write a line of code. The docs also describe reference modes, including a deathmatch and a battle royale called Cordon.
The documented systems cover vehicles, NPCs, loot, time and weather, elevators, interactions, chat, notifications, map blips and visual effects. For data that must survive a restart, server Lua can use SQLite files, which need no separate service, or the built-in bridge to MySQL and MariaDB. Note that the server download does not install a database service: a SQL database has to exist before you point the server at it.
If your team has written FiveM resources, read the FiveM compatibility page before porting. It lists the aliases that work unchanged and, more usefully, the places where OPEN//77 deliberately answers differently.
Moderation, Warden and Updates
Licensing decides whether a server is on the platform, not who may join it. Admission is your job: the docs describe passwords, community whitelists and connection rules that a server sets for itself.
For daily administration the server bundles Warden, a browser admin panel with a live console, resource reloads without a restart, warn, kick and ban tools, announcements and staff roles. Warden is off by default and gives complete control of the server, which is why the docs tell you to keep it bound to a private address and reach it through a VPN or SSH tunnel instead of exposing it publicly.
Updates deserve a routine while the platform is in Alpha. Take a backup, update the server, start it, read the log, join with a test account and only then announce that the city is open. If a resource broke, restore the backup and fix it without an audience. Keep preview builds away from your live world: they need players to switch their launcher to Unstable and are meant for testing.
What to Compare Before You Rent an OPEN//77 Server
OPEN//77 hosting is new, so offers are hard to line up. These questions do the sorting.
- Memory and CPU in the priceNo official capacity figures exist yet, so check how much RAM and what CPU speed the price includes, and what an upgrade costs.
- File accessYou will edit server.jsonc and upload resources constantly. Make sure you get full file access and SFTP.
- Both ports reachablePlayers need the game port and the resource download port. Ask whether both are open as standard.
- BackupsWith breaking changes expected during Alpha, check how backups are made and how quickly you can restore one.
- Location and pingTest your latency to the data centre before ordering, from the place where most of your players live.
- Billing termsLook for monthly billing with no minimum term while the platform is this young.
OPEN//77 Server Glossary
- OPEN//77
- The independent community multiplayer platform for Cyberpunk 2077.
- Launcher
- The player's program: it signs in, checks the game, installs the multiplayer update and lists servers.
- Master
- The OPEN//77 service that verifies license keys and keeps the server directory.
- License key
- The op77_live_ key that ties a server to its owner's account.
- server.jsonc
- The server's config file: name, visibility, network and master settings.
- Public endpoint
- The internet address and port the launcher hands to players.
- Resource
- A package of Lua scripts, a manifest and optional WebUI that adds gameplay.
- Freeroam
- The game mode template included with the server download.
- Warden
- The admin panel bundled with the server, off by default.
- WebUI
- Chromium-based interface pages a resource can ship for HUDs and menus.
- Direct Connect
- The launcher option for joining a server by IP or hostname and port.
OPEN//77 Server Help and Official Links
The official documentation, and the quickest ways to reach us.
- Host your own server, OPEN//77 docsServer.jsonc, the license key and getting listed.
- Server licensing, OPEN//77 docsCreating, linking and revoking keys.
- Open Alpha guide, OPEN//77 docsWhat to expect and how to report problems.
- Server resources, OPEN//77 docsThe resource layout and manifest.
- Gaming Deluxe control panelHow the panel works and how to log in.
- Contact support24/7 help with your server.
How this guide was made: researched from the official OPEN//77 website and documentation at open2077.net, read on 17 November 2026. Drafted with AI assistance, checked against our live order form for the plan, prices and locations, and reviewed by Matthew Griffin before publishing. OPEN//77 changes quickly during Alpha. Spotted something out of date? Tell us.
Sources, checked 17 November 2026:
- OPEN//77, official website
- How OPEN//77 works, OPEN//77 docs
- Open Alpha: play, host and build, OPEN//77 docs
- Host your own server, OPEN//77 docs
- Server licensing, OPEN//77 docs
- Server startup arguments and logging, OPEN//77 docs
- Warden, OPEN//77 docs
- Lua resources loaded by the server, OPEN//77 docs
- Configure a SQL database, OPEN//77 docs
- FiveM compatibility aliases, OPEN//77 docs
- Create a server, OPEN//77
- Gaming Deluxe order form, Cyberpunk 2077 Multiplayer (OPEN//77) Dedicated Server