SCComp Infrastructure is entering the final production-readiness stage for our commercial hosting platform.
Our full-scale production launch is scheduled for September 30, 2026 at 7:00 a.m. Eastern Time. That milestone marks the point when we begin operating the affiliate-code program alongside the broader automated service platform.
What the launch means
This is more than a website update. We have been connecting ordering, payment, inventory, provisioning, networking, customer management, and support into one operating platform. The launch milestone is when those pieces begin working together as the normal way customers purchase and manage SCComp services.
Affiliate codes will officially become operational at launch. Account-linked codes can provide an eligible customer discount while recording the referral for the account owner who shared it. Usage, attribution, commission status, limits, and payout references are tracked through the platform so the program can grow without relying on informal spreadsheets or manual guesses.
Recent platform additions
A substantial amount of production work has been completed across the customer and operator experience:
- The customer and administrator dashboards now share a consistent, responsive management design.
- The service catalog supports VPS, monthly bare-metal servers, dedicated GPU-equipped systems, and a separate foundation for future hourly on-demand GPUs.
- Monthly physical GPU systems can publish their installed accelerator model, card count, and VRAM without being confused with hourly GPU capacity.
- Customers can track orders, devices, invoices, tickets, referrals, and documentation from one account.
- Searchable documentation, comments, likes, project updates, and detailed customer guides make platform changes easier to understand.
- Proxmox-backed VPS pages provide live CPU and memory information.
- Assigned physical servers provide supported health, inventory, power, virtual-media, and browser-console capabilities through protected iDRAC integration.
- Browser consoles have received focused reliability, keyboard, paste, detach, reconnect, and session-security improvements.
Building toward complete automation
The VPS workflow has been designed around a complete chain rather than a simple “create VM” button. An eligible order can move from confirmed payment into reserved inventory, collision-safe VM allocation, cloning, resource configuration, operating-system selection, credentials, networking, guest-agent verification, device creation, and customer-visible status.
The important part is the verification boundary: a service is not presented as ready simply because a virtual machine exists. Hostname, addressing, gateway, guest connectivity, and platform state must agree before fulfillment is considered complete. Network publication is kept behind that readiness gate so an incomplete guest does not become a customer-facing service.
Physical infrastructure is following the same model. Bare-metal catalog inventory, customer assignment, controller binding, system management, notes, recovery media, and termination records are being brought into one auditable workflow. Monthly dedicated GPU servers now use that same bare-metal path. Hourly on-demand GPU service remains a distinct future phase so its metering and capacity controls can be built correctly.
Reliability and security work
Production readiness also means doing the less-visible work that keeps services dependable:
- Public forms now use layered spam, replay, timing, validation, CSRF, and rate-limit protections.
- Session boundaries, cache policy, sensitive-path handling, TLS behavior, and security headers have been hardened.
- The mail platform now uses DNSSEC, DMARC reporting, TLS reporting, CAA controls, and enforced MTA-STS with an authenticated policy endpoint.
- Service changes are backed up, validated before reload, tested afterward, and recorded in the public SCComp Platform changelog.
- Customer infrastructure management remains authorization-scoped; private management networks and controller credentials are not exposed to the browser.
What we are validating before launch
The remaining period is focused on operational proof rather than adding features for appearance. We are validating checkout behavior, provisioning retries, stock consistency, customer notifications, referral attribution, device handoff, support workflows, and failure recovery. Public-address automation will continue to move forward only when the upstream network inputs and end-to-end tests are available.
Some services will still require staff review at launch. Bare-metal systems, specialized networking, unusual IP requirements, and custom infrastructure should be expected to pass through availability and technical review. Automation should remove repetitive work without hiding decisions that need an experienced operator.
September 30
At 7:00 a.m. Eastern Time on September 30, 2026, we will begin the next operating stage of SCComp Infrastructure. Affiliate codes will become part of the active customer-acquisition workflow, and the platform improvements described here will support a more consistent path from service discovery to delivery and ongoing management.
We will continue publishing meaningful changes under Projects → SCComp Platform. Customers and partners who want to prepare for launch can review the documentation, verify their account information, and contact Sales or Support with questions about planned deployments.