Hosting sales site for SRVIA

SRVIA hosting for teams that need one brand, one identity, and two control surfaces.

SRVIA is the public face of a real hosting stack: VPS, VDS, dedicated servers, AI hosting, DNS and domain services, SSL, backups, and control panels. SHP handles customer hosting and domain operations. SCP handles infrastructure control. SRVIA ID sits in the middle so users move between the three surfaces without creating a separate account for each one.

Go to SHP Go to SCP See plans

SRVIA ID Shared login for public sales flows, SHP and SCP.

Managed stack Hosting, DNS, SSL, backups, and panel operations.

Single route Clear path from marketing page to the right console.

Service surface

Live platform model

One identity

SRVIA ID lets the same operator move between the sales site, SHP, and SCP without duplicated accounts or separate login stories.

One public brand

srvia.com becomes the actual sales surface, not a placeholder. It points traffic to the right panel when a user is ready to act.

One operating model

Public siteSRVIA.com

Customer panelSHP

Control panelSCP

What SRVIA sells

Keep the public site concrete. Sell the product lines, then route the user to SHP for purchasing and SCP for technical control.

Managed VPS

Fast VM plans, Proxmox-backed infrastructure, and migration help for teams that need a predictable entry point.

Server / VDS

More CPU, more RAM, more storage, and a clean upgrade path for heavy workloads and customer-facing backends.

Domain and DNS

Domain registration, DNS hosting, zone management, and certificate flows under one shared SRVIA identity.

AI hosting

GPU-ready project space for inference, agents, internal tools and automation workloads with clear panel access.

Backups and recovery

Snapshot policies, restore support, and clean handoffs for clients who need recovery that is not improvised.

Mail and control

Hosted service routing, panel access, and the operational tooling needed to manage customers without friction.

Cloud and app hosting

App deployment space for web apps, APIs, cron jobs, workers and internal admin surfaces.

Network services

Reverse proxy, DNS, failover, certificate renewal and monitoring as a managed service layer.

Domains, subdomains and service names

Use the public brand as the primary entry point and keep the operational labels predictable. That makes the platform easier to sell and easier to support.

Domain portfolio

These are the visible names customers will remember. Keep them short, readable and tied to the product they open.

srvia.com Main sales site. Brand, product lines, trust signals and direct action buttons live here.

Primary

shp.srvia.com Customer hosting panel. Orders, services, billing, DNS and account actions happen here.

Customers

scp.srvia.com Server control panel. Infrastructure work, deployment, admin tasks and audit trails live here.

Ops

dns.srvia.com DNS control and Technitium-facing operational access for zone work and changes.

DNS

Reserved service names auth.srvia.com, status.srvia.com and mail.srvia.com are the kind of clean labels a serious host keeps ready.

Reserve

Suggested service labels

Keep names descriptive, not clever. Customers should know what they get before they click.

VPS Hosting

Entry, growth and steady plans for websites, applications and small business workloads.

VDS / Server

Higher performance hosting for heavier sites, APIs, game servers and backend systems.

AI Hosting

Inference, model endpoints and automation infrastructure with direct panel management.

Product matrix for real buyers

The site should help someone choose the correct service in under a minute. This matrix turns searches into product selection and routes them to the right panel.

Service	Best for	What is included	Primary surface
Managed VPS	New sites, agency sites and SMB applications	Virtualized compute, domain routing, SSL, snapshots and a support path	SHP
Business VDS	Production web apps, APIs and heavier workloads	Dedicated resources, Proxmox-backed control, migrations and monitoring	SHP + SCP
Dedicated Server	High traffic, compliance and custom storage layouts	Bare-metal hardware, disk and network profile, admin workflows	SCP
AI Hosting	Inference, internal agents and automation	GPU-ready compute, containerized workloads and resource controls	SCP
Domains + DNS	Brand, zones, mail and SSL	Registration, zones, Technitium DNS, renewal and TTL control	SHP + dns.srvia.com
Backup / Recovery	Disaster recovery and restore testing	Snapshots, retention policies, restore validation and audit trail	SCP

Pricing logic

Keep price pages tied to these services so the catalog matches the way customers search: VPS, VDS, Dedicated, AI, DNS and Backup.

Service routing

Every service should have one primary surface. Sales goes to srvia.com, customer work to SHP, infra work to SCP.

Network naming

Reserve clean hostnames for user-facing actions: auth.srvia.com, status.srvia.com, mail.srvia.com and dns.srvia.com.

Infrastructure standards

SRVIA should say what it is built on. That makes the business feel real, and it gives customers a clear picture of how service, identity and operations fit together.

Proxmox virtualization

Use it for VPS and VDS workloads, snapshots, migrations and capacity control across the hosting stack.

Technitium DNS

Run zone control, delegation, TTL tuning and DNS operations from a clear operational surface at dns.srvia.com.

Keycloak identity

SRVIA ID keeps logins, recovery and policy in one place so SHP and SCP do not drift apart.

Monitoring and backup

Status, alerts, snapshot policy and restore testing belong in the operating layer, not in a ticket thread.

One identity, three surfaces

SRVIA ID is the shared login layer. The public site sells, SHP manages hosted customers, and SCP handles infrastructure operations.

Shared SSO model

The same identity provider should front both panels. That gives you one login story, one account lifecycle, and one place to enforce policy.

Public site to panel Visitors start on SRVIA.com and move to the correct console when they are ready to buy or manage.

srvia.com

Customer hosting operations SHP keeps billing, domains, workspace and customer flows in one place.

SHP

Infrastructure control SCP stays focused on the technical side of the business without splitting identity again.

SCP

Login path

The login path is intentionally short. The user sees one brand and one identity provider, then lands in the right panel.

srvia.com

Marketing site explains the offer and points the user to the right action.

SRVIA ID

Keycloak handles authentication, account recovery, and session policy.

SHP or SCP

The user returns to the target panel with a session already attached.

Plans that match the way you sell

No fake pricing here. The page is set up to present the offer clearly and hand the customer into SHP when they are ready to buy.

Entry

Starter VPS

For one site, one team, and a clean place to start without building a private stack from scratch.

Simple service bundle

Managed VPS or shared service start
Domain routing and DNS setup
Basic backup and support path

Buy in SHP

Most sold

Business VDS

For teams that need predictable uptime, panel workflows, migrations, and a clean support story.

Operational ready

Panel access for hosting and customer ops
Managed DNS, SSL and certificate flows
Shared identity across SHP and SCP

Open SHP

Advanced

Dedicated + AI

For clients with technical requirements that belong in the control panel, not in a support ticket.

Control surface

Infrastructure actions in SCP
Monitoring, audit and admin flows
Single sign-on through SRVIA ID

Open SCP

Why SRVIA wins deals

A hosting company sells reliability, clarity, and a short path to action. The site should communicate those things without sounding generic.

Fast migration path

Move existing websites, mail, DNS and application workloads without turning onboarding into a support maze.

Support that routes well

Sales requests stay on the public site, customer actions stay in SHP, technical tasks stay in SCP.

Unified identity

SRVIA ID keeps the same account across the business, so customers do not re-learn auth every time they change context.

Product clarity

VPS, VDS, dedicated, AI and domain products are named the way customers actually search for them.

How the operating layer should feel

Fast to scan, simple to navigate, and split between customer facing work and infrastructure work. That is the right shape for hosting.

Operational rules

Public site Sales, trust, product positioning and lead capture.

srvia.com

Customer panel Orders, domains, billing, and hosted workspace work.

SHP

Control panel Infrastructure, automation, and admin tasks.

SCP

Domain console DNS, SSL, zone changes and certificate renewal flows.

dns.srvia.com

What stays consistent

Brand, login, session policy, and the path from marketing to action should not change from one surface to the next. SRVIA ID makes that possible.

Same account One username, one recovery path.

SSO

Same brand Public site and panels read as one product line.

Brand

Same flow Authenticated users land where they are supposed to.

Route

Support and service model

A serious hosting brand shows how it handles help, incidents, and account work. The site should make that obvious before the first ticket.

Support channels

Keep the request path aligned to the problem so customers do not hit the wrong team first.

Pre-sale and new orders Questions about plans, migration, domains and what to buy next start from the public site.

Sales

Existing customer work Billing, service changes, DNS, hosting and panel actions go through SHP.

SHP

Infrastructure and audits Backups, nodes, automation, access and operational logs belong in SCP.

SCP

Identity and recovery Account recovery, SSO and session policy are owned by SRVIA ID.

Platform promises

What customers expect from a hosting firm is not flashy copy. It is a clear operating posture.

Transparent service ownership

Each surface owns one job and exposes the right actions, without duplicating menus everywhere.

Stable account continuity

One identity keeps the customer moving, even when they jump from sales to support to operations.

Clear expansion path

Start with a VPS, grow into VDS or dedicated, then add AI or DNS services without replatforming.

FAQ

Use these answers to remove friction before it becomes support load.

Common questions

Is SRVIA ID mandatory? No. It is the common path for SHP and SCP, but local fallback can stay available while you transition users.

Which panel should customers use? SHP for customer hosting and purchases, SCP for infrastructure control and admin-level actions.

Routing

What should `srvia.com` do? Sell the brand, explain the product, and push the visitor toward SHP or SRVIA ID when they are ready.

Sales

Where do domains live? Domain sales and DNS actions should sit in SHP, while technical DNS operations can also surface in `dns.srvia.com`.

Domains

Next actions

When you are ready, the public site can link straight into product detail pages, calculators, migration intake, and a real support contact form instead of just button links.

Price pages Detailed VPS, VDS and dedicated tiers.

Migration intake Collect stack details before moving a customer.

Support center One place for tickets, docs and status.

SRVIA is ready to act like a real hosting brand.

The public site sells the stack, SHP handles customer hosting, SCP handles infrastructure, and SRVIA ID keeps the login boundary consistent across all three.

Open SHP Open SCP Enter SRVIA ID