Provisioned lab infrastructure
Spin up safe labs for controlled failure.
Provisioned environments for testing, learning, and controlled failure, with clear boundaries before anything reaches production.
- Families
- 5
- Network
- v6 / v4 / NAT
- Setup
- 1–15 min
Product Catalog
Virtual Lab Infrastructure
Nested labs for controlled failure.
Experiment-grade environments. Break things, rebuild, repeat — without touching production.
View architectureDedicated Compute Matrix
Predictable VMs with hard boundaries.
KVM machines for steady workloads. Public IPv6, on-server snapshots, clear limits.
View architectureElastic Deployment Layer
Scale paths from NAT to cloud.
CloudLabs, ElasticLabs, and NAT tiers. Grow disk and network as the work expands.
View architectureVirtual Labs bill in LAB Coin — 100 free at signup. Other families bill in IDR. Final price and stock are confirmed in the panel.
Open client panelSystem Architecture
Structured lab infrastructure with clear boundaries before deployment.
- I
Base lab
Nested or dedicated environment, provisioned in 1–15 minutes.
- II
Network boundary
Public IPv6, IPv4, or private NAT — scoped per product family.
- III
Provisioning layer
Snapshots and recovery context. Keep your own backups.
- IV
Client panel
Stock, billing unit, ordering, and support from my.8labs.id.
Order, deploy, and manage from one panel.
Live stock, billing unit, and final price are confirmed in the client panel before anything provisions.
Active labs
12
LAB Coin
340
Avg setup
6 min
| Instance | Network | State |
|---|---|---|
| virtual-lab-01 | IPv6 | Running |
| vdl-prod-2 | IPv4 / v6 | Running |
| elastic-nat-7 | NAT | Provisioning |
Clear signals before users deploy workloads.
Labs are built for experimentation, not production guarantees. Status, docs, backup expectations, and support paths — stated plainly, no invented SLAs.
Status link, with fallback awareness
The site links to a public status route for availability checks. If that route has a certificate or availability issue, use the client panel or community path instead.
Open statusDocs and support path
Product usage should start from the docs at 8labs.id/docs. Account, provisioning, or incident-specific issues belong in the client panel support path.
Read docsBackup expectations
8Labs terms state that users should perform their own backups and that backup availability or integrity is not guaranteed. Treat snapshots as convenience, not external backup.
Review termsConservative security claims
Public product pages mention DDoS or Anti-DDoS on selected product families. Security, abuse, or account-impacting reports should go through support with context.
Contact supportTrust Verification
Verified community trust signal.
Showing only verified public trust assets. No invented customers, no filler logo wall.
Image Compatibility