Infrastructure and Security
Cloud hosting
Real cloud work is not “spin up a VM”: it is picking the right region, private networking when it matters, backups that actually restore, and costs finance can read. Viscale treats hosting as part of the product — same SLA language, same care for traffic spikes, and the same goal of leaving your team knowing what to tune when it gets hot.
Infrastructure that matches business risk. We map what runs today (or what will run), honest CPU, memory, and disk for the first cut, and how to split staging from what customers touch. No “giant instance because it is easy”: we size with a real margin and alerts before the disk fills at 3 a.m.
What we can host for you
APIs and backends in containers
Light or managed orchestration, health checks, and rollouts without killing sessions.
Sites and landings with CDN
Sensible cache, compression, and auto-renewed certificates.
Managed database + app in the same VPC
Internal traffic, point-in-time backups, and a rehearsed restore.
Staging that mirrors prod
Anonymized or subset data so releases are tested without fear.
Queues and workers for peaks
Black Friday, campaigns, or overnight batches without freezing UX.
File and media storage
Versioning, lifecycle for cost, and signed URLs when data is private.
Provider or region migration
Windowed plan, DNS, and rollback if latency misses the mark.
Minimum viable observability
Metrics, logs, and an alert that reaches the right person.
Network, access, and secrets in the right place. Bastion when needed, tight security groups, TLS end to end, and secrets outside source. As the team grows, we document who holds which keys — so nobody depends on one person’s memory.
Stacks and practices you can audit. We work with mainstream cloud vendors (AWS, GCP, Azure, or your company standard), Terraform or equivalent when it fits, deploy pipelines, and centralized logs so you see latency, 5xx errors, and queue depth in one place. The CTA is simple: talk to us and plan the next move without fluff.
Portfolio of Cloud hosting
Deliverables
Production environment
As approved, with HTTPS and agreed networking.
IaC repo or folder
What stood the environment up, versioned.
Cost map by service
So finance can follow without surprises.
Documented backup policy
Frequency, retention, and how to request restore.
Restore test report
Date, duration, and objective outcome.
Monitoring dashboards
Links plus plain-language explanation.
Alert list and recipients
Who gets what and on which channel.
Credential register (outside Git)
Where keys live and who can access.
Basic security checklist
Ports, SGs, TLS, and least privilege.
Handoff session
Q&A with the team that runs day two.
Execution methodology
-
Inventory what exists
Services, traffic, current cost, and the real pain (slow, expensive, fragile).
-
Target architecture
Network, zones, names, and what stays public vs private.
-
Sizing and cost
Honest first cut + how to scale when metrics climb.
-
IaC or reproducible checklist
So the next environment matches the first.
-
Secrets and access
Vault, roles, rotation — no passwords in README.
-
Backup and restore drill
Proof you can recover, not “backup for show”.
-
Deploy and pipeline
Build, basic automated tests, and promotion across envs.
-
Monitoring and alerts
Dashboards and thresholds agreed with product.
-
Go-live and hypercare
Checklist window with someone who knows the stack.
-
Docs and handoff
Short runbook: where to click, what to restart, who to escalate.
