Your server.
Your app.
Your features.
AI support that resolves what your players ask. An app they run their own actions from. Shops, traders and factions that run themselves. A panel where your staff finish an investigation instead of starting one. And when you want something that doesn't exist yet, you describe it and it gets built into your server — yours only.
For private DayZ servers on Xbox and PlayStation, hosted on Nitrado.
Everything on your server waits for you.
You started it because the public servers were a mess and you thought you could run a better one. You were right. Then you became the queue everything sits in.
Players wait on staff
A base claim, a transfer, a shop order — all of it stops until somebody with permissions wakes up and reads Discord.
Staff wait on logs
Two players, two stories, and a raid log nobody can read fast enough to settle it before one of them quits.
You wait on a developer
The one feature that would make your server different needs somebody to write it. So it never gets written.
The same question
"How do I claim my base?" Asked again. In general chat. By someone who won't read the pinned message either.
Fragile config
One misplaced comma in a file you're editing by hand over FTP and the server won't come back up. On a Friday.
Your own money
You pay for the box, the mods and the hours. The community grows, the workload grows, the help doesn't.
Describe it. Your server gets it.
On console, configuring the server is the job — so we made the job a conversation. Change what your server already has by asking for it, and when you want something that doesn't exist anywhere yet, describe that too. It gets built into your hub and your app, for your server only, without waiting on a developer's queue.
- types.xml12 values changed
- events.xml1 event added
- cfgeventspawns.xml4 positions added
<type name="AKM"> - <nominal>8</nominal> + <nominal>20</nominal> - <min>4</min> + <min>10</min> </type>
The file names and fields above are the real ones you'd otherwise be editing by hand.
Nobody should have to learn XML to run the server they paid for.
Loot, events, spawns, raid windows, rules. Ask in plain English, get valid config back, see it as a diff against what you're running now.
Describe a system your community wants that nobody has built — a ranking, a reward, an event loop — and it becomes part of your hub and your app. Not a shared feature request queue.
Nothing reaches your server on its own. Config is backed up before deploy, and if the server doesn't come back up clean, it rolls back by itself.
- 01Generate
- 02Validate
- 03Diff
- 04Approveyou
- 05Backup
- 06Deploy
- 07Restart
- 08Verify
- 09Auto-rollback
Four queues, closed.
Grouped by who stops waiting rather than by subsystem, because that's what actually changes when you turn it on.
Members act for themselves
Most of what lands in your Discord is a request somebody already has the right to make. It shouldn't need a human to press the button.
Answers from your server's own rules, shop and setup — and resolves most of what comes in without anyone else reading it.
Claims, transfers, requests and lookups your members complete themselves, inside the permissions you set.
Rules, schedules, prices and guides posted where players already look, and kept current when you change them.
Generated from your current settings rather than typed once and left to rot in a pinned message.
Shops, traders and NPCs run themselves
Three ways to sell, all automated, all managed from one place instead of a spreadsheet and a weekly reconcile.
Stock, pricing and orders handled end to end. Players buy, the system records it, nobody chases a receipt.
Automated traders with their own inventories and prices, running to the rules you set rather than to your availability.
NPC vendors placed, stocked and priced from the panel — no coordinate maths, no hand-built camps.
Player currency, rewards and payouts tracked by the system, so the ledger isn't a channel you scroll.
Groups, ranks and activity, checked automatically
Factions are the reason people stay. Keeping them honest is the reason owners burn out.
Creation, membership, ranks and standings handled as a system rather than a spreadsheet and a trusted volunteer.
Inactive factions and dormant members flagged on their own, so slots free up without you auditing anything.
Standings, bounties and rivalries built from log data — the numbers your community argues about all week.
Per-player records and kill history, built from your server's own log output and posted minutes after the action.
Your setup, your schedule, your features
The parts that make your server different from the one next to it — and the tooling to change them without opening a file.
Describe a feature that doesn't exist and it gets added to your hub or your app, for your server only. See how →
Restarts, wipes, events and raid windows on a calendar. Base damage on and off by schedule, not by you, awake, at the right moment.
Generated from your types.xml and events.xml — your server's real loot and events, not a generic Chernarus map.
The AI walks you through it and does the configuring. No XML knowledge, no weekend lost, no documentation to read first.
Your community, in their pocket.
Your players get an app for your server. They sign in with Discord, it works out which subscribed servers they're in, they pick yours — and everything after that is your content, your shop, your factions, your branding.
Not a directory of other people's servers with yours listed in it. Discord still works for everyone who prefers Discord; the app is where the players who want more go and get it.
Browse, buy and check balances from a phone instead of typing commands into a channel and waiting.
Their kills, their faction, their rank and the leaderboard they're chasing — the things that keep people logging back in.
Ask a question and get a real answer. Run the actions they're allowed to run. No ticket, no queue, no waiting on a moderator.
Features you described and had built land here too — so your app has systems no other server's app has.
Your staff finish investigations. They don't start them.
Cheaters and rule-breakers get caught by reading logs nobody has time to read. The panel does the reading, assembles the evidence, and hands your admins a decision to make — with the extract attached.
Every action in this exchange is a proposal waiting on an admin. Nothing in it is enforced by the AI.
Searches the event log over the window in question, checks raid activity, player presence and base protection status. The digging that eats your evening happens before you're involved.
Bans, warnings and compensation arrive as proposals with the evidence attached. Your admins approve or reject. Nothing is enforced by the AI on its own.
Detection runs on the output a console server actually gives you, and the resulting ban goes out through the Nitrado API.
Every outcome keeps the evidence it was based on, so "the admin is biased" becomes something the player can read for themselves.
Connected and configured the same evening.
There's no mod to install, because on console there can't be. Everything runs through the channels a stock Nitrado-hosted server already gives you — and the AI does the configuring.
Connect Discord
The Discord you already run. Support, orders, approvals and alerts all arrive there — nothing new for your players to learn.
Connect your server
Link your Nitrado-hosted server so config can be read and written and your logs can be parsed. Nothing is installed on the game server.
Let it set itself up
Answer questions in plain English and the AI does the configuring. No XML, no documentation, no weekend.
Stop being the queue
Players self-serve, support resolves itself, the economy and factions run, and your staff only see decisions.
Console first, not console-also
Built for private servers on Xbox and PlayStation, hosted on Nitrado — where the tooling has always been thinner, the platform more locked down, and the admin work heavier.
We run these servers.
This isn't tooling designed from the outside. We've been running console DayZ servers for years, and everything here exists because the problem hit us first and we got tired of solving it by hand.
DZAI also runs DayZ Console, our own community — which is where most of these problems were found, argued about and eventually fixed.
Two levels, split by read and write.
One level covers everything DZAI reads out of your server and hands to your players and staff. The other adds everything that writes back into it — the copilot and the modules that run on the same pipeline.
Nothing is written back
- AI support & info channels
- Your community's app for players
- Killfeed, stats, leaderboards & standings
- Staff panel — investigations & evidence
- Loot & event map from your config
Everything opposite, plus
- Build from a sentence — new features for your server only
- Config changes by asking, with the nine-step chain
- Automated shop, trader shop & NPC shop
- Faction system & activity checking
- Self-service actions for members
- Scheduled operations & raid windows
- Moderation actions issued to your host
Before you ask.
The ones that come up every time an owner hears "the AI does it".
Two things. Changing what your server already has — loot, events, spawns, raid windows, prices — happens by asking for it, and you approve a diff before anything deploys.
Adding something that doesn't exist yet is the same conversation: you describe the system you want, and it becomes part of your hub and your app. It belongs to your server, not to a shared roadmap everyone votes on.
It doesn't get to decide on its own. Every change is generated, validated against your current config, and shown to you as a diff. You approve, or you reject.
If you approve: your config is backed up first, then deployed, then the server restarts and gets verified. If it doesn't come up clean, the change rolls back on its own. Nine steps, none of them skippable.
Yes — that's the point of it. It answers from your server's own rules, prices and setup rather than a generic FAQ, so most of what your players ask gets resolved without anyone else reading it.
What it can't close arrives with the context already gathered, so your staff pick up a decision rather than an investigation.
No. Discord is the channel that has to work and everything runs there. The app is for the players who want more: they sign in with Discord, it finds the subscribed servers they're in, and they get your community's shop, stats, factions and support.
Private DayZ servers on Xbox and PlayStation, hosted on Nitrado — the mainstream console host, and the platform everything here is built around.
No — and on console you couldn't have them anyway. Server mods are blocked at platform level. Everything here works on a stock server through config, log output and Discord.
A command bot does what you type, when you type it. It doesn't write your server config, it doesn't investigate a raid, it doesn't give your players an app, and it certainly doesn't build you a feature nobody else has.
That's a different category of tool.
Stop being the thing your server waits for.
AI support, an app for your players, an economy and factions that run themselves, a staff panel that decides — and any feature you can describe.