ageLANServer: Age of Empires lobbies without the official servers
Web Server (and its launcher) for AoE 1, 2, 3 (all DE), AoE 4 and AoM: RT supporting offline multiplayer, fully cross-platform and portable
At a glance
- What is it?
- ageLANServer is a Go web server plus launcher that hosts Age of Empires multiplayer lobbies when the official servers are in maintenance or gone. It reproduces much of the lobby layer, and it leaves matchmaking, achievements and clans unimplemented.
- Who is it for?
- Adopt ageLANServer when you own the games and want to keep playing multiplayer on a LAN or a self hosted box after the official servers become unavailable, and when you can also run its launcher with the elevated rights it asks for. Do not adopt it if your group depends on matchmaking, achievements, clans, leaderboards or friend lists, because the project states those are unimplemented.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Go, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 20, 2026, and from our analysis. They are not legal advice.
Editorial analysis
Multiplayer lobbies when the official servers are down
Age of Empires titles in the Definitive Edition family route multiplayer through a hosted service, which means the lobby layer disappears when that service is in maintenance or eventually shut down. The project description states the aim directly: a web server, with its launcher, that lets you play multiplayer lobbies without a connection to the game server, so that multiplayer keeps working even if the official server is in maintenance or is eventually closed. The former name, AoE 2 DE LAN Server, makes the original intent clear, and a note in the README says the tool is not strictly limited to LAN only, so a machine reachable over a home network or a tunnel is the normal deployment. The audience is players who own the games and want a self hosted lobby, not a general purpose game server emulator.
A Go workspace split into server, launcher and battle server
The repository layout shows a multi component Go project rather than a single binary. There is a go.work file at the root, and the tree separates server/, launcher/, launcher-agent/, battle-server-manager/, battle-server-broadcast/, common/, config/, config-helper/, launcher-config/, launcher-config-admin/ and launcher-config-admin-agent/, plus server-genCert/, build/ and tools/. The naming suggests a clear division of labour: a server side that speaks the game protocols, a launcher side that prepares the client, an agent that runs alongside the launcher, a battle server manager and broadcast component, and shared code in common/. A separate server-genCert/ directory and a release_public.key file point to release signing and certificate generation handled inside the build, which matches the README statement that listening on port 443 for https will probably require admin rights or firewall permission depending on the operating system and configuration.
What the lobby layer actually reproduces
The feature list is long enough to show that this is more than a stub. The general set covers scenarios, map transferring in lobby, restore game, data mods, lobby chatting and crossplay between Steam and Xbox. Several games add more: observing for AoE II DE including CapturAge, lobby invite, share lobby link and player search, Co-Op campaigns and rematch for AoE II DE and AoE III DE, channels and whispering for AoE II DE, groups for AoE III DE and AoE IV AE, and whispering plus Arena of the Gods for AoM Retold. The ageLANServer wiki page called Questions and Answers is where the README says to find more detail. Support is explicit too: Age of Empires Definitive Edition, Age of Empires II Definitive Edition, Age of Empires III Definitive Edition, Age of Empires IV Anniversary Edition and Age of Mythology Retold, the last of which currently supports only the Steam version.
Downloading the binaries and hosting a first lobby
The README points at the releases page for binaries, and the recent tags are v1.15.6 from 2026-10-11, v1.15.5 from 2026-09-22 and v1.15.4 from 2026-09-20. No build or run command appears in the documentation excerpt, so the honest first step is to take a release build for your platform, place the server and the launcher where the system requirements allow, and open port 443 for https, which the README says will likely need admin rights or a firewall exception. The repository ships a .env.example with two keys that are empty by default, and you would fill them for your own deployment.
GPG_FINGERPRINT=
GOROOT_LEGACY=The excerpt does not explain what either key controls, so treat them as configuration to be filled in rather than switches you can guess at. On the client side the README recommends reasonably current game builds: a 2025 version or later for Age of Empires IV Anniversary Edition and Age of Mythology Retold, a late 2023 version or later for Age of Empires III Definitive Edition, and a mid 2024 version or later for Age of Empires II Definitive Edition, while noting that older versions have known issues. For development work the tree also carries Taskfile.yml and several Taskfile variants for debug, tools and mock tasks, which is the go-task entry point rather than a Makefile.
The launcher is the part that needs elevated rights
There is an important caveat sitting above the whole project, marked as important in the README: you still need a custom launcher to bypass the online-only restriction that the game imposes for connecting to the internet and Steam or Xbox Live, depending on platform and version, in order to play fully offline. The author points at a separate companion project that provides the files and information to download a Steam Emulator and play 100 percent offline. The ageLANServer launcher itself also has needs: the note says that if you allow and it is needed to handle the hosts file, a local certificate, or an elevated custom game launcher, it will require admin rights elevation. Server side minimums are stated too, from Windows 7 or equivalent and Linux kernel 3.2 to macOS Monterey v12, with newer versions recommended, and experimental support listed for BSD, Solaris and AIX.
Matchmaking, achievements, clans and other empty menus
The project is candid about what it does not do, which is what makes it usable for planning. Matchmaking is unimplemented, on the reasoning that an ephemeral server with limited users makes little sense for it. Achievements are left to the official server, with the note that meeting achievement requirements during a match might cause issues. Leaderboards appear empty, clans place all players outside clans so browsing shows nothing and creating one errors, and lobby ban plus report or block appear to work but do not. General limitations add that joining a lobby from a link only works if the game is already running, that subscribing to online mods only works with the official launcher, and that there is no Xbox and Steam friend integration. For Age of Empires III DE and IV AE the friend list shows all online users as if they were friends, and for Age of Mythology Retold Arena of the Gods grants no rewards, unlocks all blessings and rarities by default including ones the official server does not offer, and leaves the favor stash infinite.
AGPL-3.0 licensing and a steady tag cadence
The licence identifier is AGPL-3.0, and the repository root carries a LICENSE file along with CODE_OF_CONDUCT.md, SECURITY.md, CONTRIBUTING.md and DEVELOPMENT.md, so the project ships the usual governance and development documentation. If you run a modified version of the server as a network service, the AGPL obligations are the part to read carefully yourself, and the LICENSE file is where to read them. The repository is not archived, and the last push was on 2026-10-19, after the v1.15.6 tag dated 2026-10-11, with two more tags in September. The comparison worth making is with the official services: they provide matchmaking, achievements, clans, leaderboards and friend integration out of the box, and they require an internet connection to the game server. ageLANServer trades all of that for local hosting and continued play when those services are unavailable.
Editorial conclusion
Adopt ageLANServer when you own the games and want to keep playing multiplayer on a LAN or a self hosted box after the official servers become unavailable, and when you can also run its launcher with the elevated rights it asks for. Do not adopt it if your group depends on matchmaking, achievements, clans, leaderboards or friend lists, because the project states those are unimplemented. Before you rely on it, confirm that your clients run the recommended game versions, that you can open port 443 for https, and that every player is prepared to use the companion launcher project that the README points to for the online-only restriction.
Frequently asked questions
Which games does ageLANServer support?
Age of Empires: Definitive Edition, Age of Empires II: Definitive Edition, Age of Empires III: Definitive Edition, Age of Empires IV: Anniversary Edition and Age of Mythology: Retold. For Age of Mythology: Retold only the Steam version is currently supported.
Do I still need an internet connection to play with ageLANServer?
No connection to the game server is needed, but the README states that you still need a custom launcher to bypass the online-only restriction tied to the internet, Steam or Xbox Live, depending on platform and version. It points to a separate companion project that provides the files and information for a Steam Emulator.
Which features are not implemented in ageLANServer?
The README lists matchmaking, achievements, leaderboards, clans, lobby ban player and report or block player as unimplemented. Leaderboards appear empty, clan creation always errors, and the ban and report menus appear to work but do not.
What does the ageLANServer server need to run?
The README lists Windows 7 or equivalent, Linux kernel 3.2 and macOS Monterey v12 as minimums, with newer versions recommended. Admin rights or firewall permission to listen on port 443 for https will likely be required depending on the operating system and configuration.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/luskaner-agelanserver)Was this useful?