Get help with your DayZ server workflow
Find the fastest path for setup questions, billing questions, server safety concerns, and bug reports. Signed-in users can also send feedback from the floating button inside the editor so the report includes the page they were on.
Getting Started
Create an account, choose a plan, and use onboarding to create or import your first project.
- Use ZIP upload for a manual project workflow.
- Use SFTP when you want pull and push access.
- Use the Windows Host app when you want live server operations.
DayZ University
Use DayZ University when you want guided learning instead of a quick answer: DayZ admin basics, Windows Host setup, mod workflows, and safer server operations.
- Follow learning tracks by topic.
- Use screenshot-led guides and short walkthroughs.
- Sign in to use the in-app DayZ University progress tracker.
Windows Host Setup
Install the Windows Host app on the machine that runs your DayZ server, then connect it from the Hosts area after signing in.
- Keep one host separate from another.
- Review server identity before saving changes.
- Use the Hosts area to confirm the installed version.
Projects And Mods
Projects hold the editor working copy. Server-bound projects can sync detected mods and expose the matching editors.
- Use Re-pull from Server before major edits.
- Use Sync Mods to mirror tracked project mods into toggles.
- Use Save Changes before deploying edits.
Billing And Plans
Billing is handled through Stripe. You can manage your active subscription from the billing area after signing in.
- Monthly and annual billing are supported.
- Access continues through the current paid period after cancellation.
- Partial-period refunds are not offered except where required by law.
Safe Server Changes
Before deploying to a live server, confirm the selected host, server, project, and pending file changes.
- Keep backups before risky changes.
- Review diffs before pushing config edits.
- Watch command results before starting another operation.
Report A Problem
Email support with what happened, what you expected, and which server or project you were working on.
- Include screenshots when they help.
- Do not send passwords or private tokens.
- Use the in-app feedback button for page-specific reports.