Mark revoked
Operator clicks revoke in the vendor console for the target license.
Axix Hawk
How it works
From SDK embed to licensed deployment
Three steps. No honor-system keys. Cryptographic binding from day one.
Three steps to first license
Most teams ship in under 15 minutes after console setup.
- 01
Register & embed SDK
Define your product in the Hawk console and embed our lightweight client libraries. Most teams ship in under 15 minutes.
- 02
Deploy to client hardware
Push a signed, distroless Docker image. Each license is cryptographically bound to the client machine fingerprint — not a reusable key.
- 03
Control from one dashboard
Renew, revoke, and monitor every deployment. Heartbeats every ~30 minutes; revoke takes effect within one cycle. Full audit trail.
ARCHITECTURE
Vendor console → Platform API → Agent → License blob → Customer machine
The control plane stays with you. The enforcement plane runs on customer hardware — online, hybrid, or air-gapped.
What happens on revoke
Remote kill-switch without a truck roll.
Next heartbeat
Agent phones home (~30 min). Revoke takes effect within one cycle.
Immediate path
Container restart exits immediately when the revoked state is loaded.
Audit
Append-only log records the revoke event for finance and security.
Operator touchpoints
Validate install health without fragile custom checkers.
Issue license
Bind a signed blob to the machine fingerprint from the vendor console.
Check agent health
Read local status from the agent — license state, machine ID, and grace window.
Revoke in console
Mark revoked once; enforcement lands on the next heartbeat or restart.
Who owns each plane
You (vendor)
Console, product definitions, signing keys, revoke policy, white-label UX.
Hawk platform
License issuance API, heartbeat intake, webhooks, multi-tenant isolation.
Customer machine
Agent, license blob, SDK gates, optional Falco runtime rules.
Why not build it yourself?
| Capability | Axix Hawk | Build your own |
|---|---|---|
| RSA license signing | Included | 2–4 weeks |
| On-prem agent + grace | Included | 4–8 weeks |
| SDKs | Included | 4–6 weeks / runtime |
| White-label console | Included | 8–16 weeks |
| Falco + hardening | Included | 4–8 weeks |
| OT SIEM/SOAR | Pipeline included | 6–12+ months |
| Time to first license | ~30 minutes | 6–12 months |
Teams ship safer with Hawk
“We went from honor-system license keys to hardware-bound deployment in a week. Zero unauthorized installs since.”
“The kill-switch saved us when a client stopped paying. Revoked at 2pm; their instance was down before end of day.”
“Distroless images plus cosign signing let us pass a security review we had failed twice before.”
Define the product once
Model seats, tiers, and feature flags in the Hawk console before you ship binaries.
- Product and tier configuration
- Client org separation
- Feature gates ready for embed
Deploy the agent beside your runtime
Local verification and heartbeats stay close to the workload.
- Offline-capable verification
- Heartbeat to the vendor console
- Status checks during bring-up
Operate revoke and renew
Day-2 operations stay in one place — no emergency SSH hunt.
- One-click revoke
- Renew without reinstall
- Webhook fan-out to ops tools
Walk the flow on a trial
Use a free trial to rehearse issue → bind → revoke before customers see it.
- Sandbox client org
- PoC checklist included
- Upgrade when ready
How it works FAQ
Most teams define a product, issue a license, and gate a feature within a working session.
Walk the architecture with us
30-minute demo — licensing, agent, revoke, and deployment security for your stack.
Product visuals
Three console views and three real-world moments for this page — each with a full caption.
Console view for How It Works: license inventory, bind status, and org filters in one workspace. Operators scan Active versus Revoked rows, confirm machine fingerprints, and jump into a client without leaving the grid. Search and column controls keep large fleets readable. This frame is unique to this page so the visual story matches the URL you opened.
Second dashboard for How It Works: heartbeat health, revoke timing, and anomaly hints sit side by side. Use it to brief security on what “one heartbeat” looks like before a PoC. Charts stay light-themed with navy accents for Axix Hawk. Nothing here is reused from another marketing route.
Third console moment for How It Works: deployment analytics and seat pressure across client orgs. Leaders see where licenses concentrate and where renewals are due. Export-friendly layout supports review packs. Paired with this page’s copy so buyers never see a generic stock screen.
People moment one for How It Works: practitioners reviewing Hawk controls in a real workspace. The scene grounds licensing talk in day-to-day operations instead of abstract icons. Lighting and wardrobe stay professional and brand-safe. Captured specifically for this page’s narrative so visitors never confuse it with another product route.
People moment two for How It Works: collaboration around ship-or-hold decisions after a revoke drill. Teams align on evidence — bind failure, kill-switch timing, audit export — before a customer demo. Atmosphere matches Axix Hawk’s light navy product language. Unique to this route’s gallery.
People moment three for How It Works: field or office context for how this capability lands with buyers. Use it to show human stakes behind machine-locked software. Composition avoids logos and keeps faces secondary to the work. Written and imaged only for the How It Works page experience.