Software for gaming communities

Less managing. More playing.

LAXIS builds tools for people who run game communities. We bring server data and alliance schedules into one place, so leaders spend less time checking and coordinating.

Open WOSMateSee the product
WOSMate is liveSupporting 2 Whiteout Survival servers

Company

We turn the daily work of running a community into tools.

Running a game community means keeping track of members, schedules, maps, and a server that never stops changing. LAXIS brings that information together to support the calls leaders make every day.

Where the name comes from

LinkConnect scattered information,

Axisgive decisions a reference point.

  • See your server at a glance

    Player records, alliance information, and server status on one screen.

  • Run your alliance in one place

    Announcements, event schedules, and placement plans the whole alliance can see.

  • Built from customer requests

    Requests from paying alliances decide what we build next.

We started with Whiteout Survival and plan to expand to other game communities.

Our first product

WOSMate

A web service for Whiteout Survival alliance leaders.

Live

Look up server maps and players, and manage alliance announcements and event schedules in one place. WOSMate is our first paid product.

  • Server maps, player lookup, and alliance information
  • Alliance announcements and event schedules
  • Placement planning and resource-gathering status
Open WOSMate

Currently available in Korean.

WOSMate alliance home showing announcements, stronghold schedules, and alliance events
WOSMate alliance home, October 2026

Operating footprintAs of October 2026

Servers supported
2
Server-level contract
1
Additional paying alliance
1

Claude roadmap

We’re building a chatbot that answers from your records.

Leaders will ask how their server or alliance has changed, and Claude will look up WOSMate records and explain the answer with its sources.

Planned

Example question

What changed in our alliance compared with last week?

How answers will work (in design)

  1. Ask

    Pick a period and ask about players, alliances, or the server.

  2. Look up records

    MCP tools find the relevant records. Backend tools compare and aggregate the numbers.

  3. Explain with sources

    Claude shows which records it used, and says so when data is missing.

  4. Leader decides

    The chatbot suggests what to look at. The leader makes the call.

Technical setup

In use today

We use Claude for software development and an in-house harness for platform operations. Our LLM gateway is already running.

Next

Connect the Claude Messages API to our data tools through MCP, and apply prompt caching to shared game context. We will check accuracy, latency, and cost with current customers before expanding to other games and external APIs.