Everything after the purchase.
Licensed teams get the manuals, the release train, and a direct line to the people who build the platform. No ticket portal, no tiered queue — one mailbox, answered by engineers. The resources below are arranged the way a new team consumes them: install, learn, operate, renew.
Manuals and references.
Two kinds of material exist: what ships with the license, and what this site can say in public. Both are listed here so you always know which door to knock on.
Installation & quickstart licensed bundle
Ships in the delivery archive. One server binary, one YAML config, a systemd unit — a single-core VPS with 512 MB of RAM runs a full teamserver. The quickstart walks from first boot to first check-in in about fifteen minutes, including the optional Cloudflare Worker front. The panel is served by the server itself; there is nothing else to install.
Operator manual licensed bundle
The in-depth manual: every build parameter, the wire format, OPSEC guidance per capability, delivery and visibility controls, and the per-platform notes that this site deliberately omits. Updated with every release; the revision in the archive always matches your build.
Capability reference public
The public fifty-three-entry reference on this site — what each capability does, which hosts it applies to, and how it appears in the console. It states scope and limits; implementation detail stays in the licensed manual.
capabilities.html 04The console walkthrough public
Every view of the panel, drawn from the product itself — dashboard, workspace, builder, stagers, campaigns, files, tunnels, audit. The fastest way to orient a new operator before the manual arrives.
console.htmlRelease train and research.
Release notes
One release a quarter, fixes as needed — every release included in the license term. The changelog carries the public revision history; per-build detail ships in the licensed notes.
/02Research notes
Detection research from the implant side: EDR telemetry maps, our BYOVD driver research, design doctrine. Written to be useful to defenders too.
/03Technical notes by email
A short email when a release ships or a research note publishes — nothing else, no marketing. Ask to be added; leave any time with one reply.
Opening a case.
Cases are email threads with the engineering team. Write to [email protected] with the subject AXIS support. The more of the checklist you include, the faster the first useful reply.
Identify the install
License ID, public revision (from the panel footer), server OS, and how long the install has been running. No license ID — no problem, the email address you licensed with is enough.
Describe expected vs. actual
What you did, what you expected, what happened instead. Agent profile, target OS and build, and the traffic profile in play matter more than screenshots.
Sanitize before you send
Strip client names, target identifiers, and infrastructure addresses from logs before attaching them. We would rather ask for a second, cleaner log than hold your client's data at all.
Server down or fleet unreachable
Same-day response, any day of the week. Say so in the subject line — AXIS support · SEV1 — and include whether agents are failing over to Ghost Chain, since that changes what we tell you first.
Defects, questions, guidance
First response within two business days, usually faster. OPSEC questions are welcome — asking before an engagement is cheaper than asking after.
License renewal.
When a term lapses, the platform closes cleanly: agents stop tasking, the panel stays readable, and your data and artifacts stay yours. A renewal command brings the same install back — no rebuild, no re-enrollment of the fleet.
Renew
Email [email protected] with subject AXIS renewal from your licensed address. Continuity pricing applies when you renew before the term ends.
email 02What the license includes
Teamserver, panel, both agents, every module, the desktop client, the toolchain, and every release in the term — the whole platform.
licensing.html 03Terms & acceptable use
The legal page: who we sell to, what the license permits, and the lawful-use conditions every customer signs up to.
legal.htmlNot a customer yet? Request an evaluation — evaluation licenses go to qualified teams on request.
One mailbox. Engineers on the other end.
Support, renewals, evaluations, and press all start at the same address. Write in English or Russian.