Alsycon
Admin Console
Dashboard

Operations

CustomersService FleetVPSDedicatedDomainsIPAMIP TransitConnectivityOrders

Billing

Billing OverviewInvoicesQuotesPaymentsProductsVAT / BTW

Support

TicketsKnowledge BaseEmail LogEmail Templates

Infrastructure

NetworkGlobal IPAM

System

IntegrationsReportsSettings
SystemIntegrationsTenantOS

TenantOS

Provisioning automation for compute. This is where real server lifecycle actions hook into the platform — create, suspend, reinstall and rescue are dispatched to TenantOS.

Demo

Connection

Point Alsycon at your TenantOS control plane. A read/write API token is required to dispatch provisioning jobs.

Demo

Base URL of your TenantOS control plane.

Read/write token with provisioning scope.

Auto-provision new orders
Dispatch a provisioning job the moment an order is marked paid.
Sandbox endpoint configured

Service Type Mapping

How each Alsycon service type routes to a TenantOS provisioning module.

Alsycon ServiceTenantOS ModuleProvisioning
VPS
KVM / Proxmox VE
Create, suspend, reinstall, rebuild
Automated
Dedicated Server
Bare Metal · IPMI
Power control, OS deploy, rescue mode
Automated
Domain
Registrar Bridge
Provisioned via registrar API, not TenantOS
Manual
Subnet / IPAM
IP Manager
Allocate, assign, set rDNS
Automated
IP Transit
BGP Session Manager
Configured by NOC on the edge routers
Manual
Connectivity
Circuit Provisioning
Last-mile order placed with carrier
Manual

Why TenantOS

Every power action, reinstall and rescue request raised from a customer's VPS or dedicated server detail page is queued here and executed against TenantOS. In this demo the jobs are simulated, but the integration surface is identical to production — swap the sandbox token for a live one and provisioning goes live without any UI changes.