Invisible foundations
keep your site steady.
We plan deployment, acceleration, backups and monitoring around your site’s size and visitor regions, and set out the maintenance scope and how we respond in the service plan.
$ piicube deploy --site yourstore.com
› Create cloud server · 4 vCPU / 8 GB done
› Install runtime · Nginx · PHP · MySQL done
› Issue SSL certificate · Force HTTPS done
› Connect global CDN · Edge nodes done
› Warm cache · Convert images to WebP done
✓ yourstore.com is live · First screen 1.2s sample
- L1Global acceleration
- L2Speed optimization
- L3Security
- L4Backup & recovery
- L5Monitoring & alerts
The right acceleration setup cuts wait times across regions.
A global CDN caches your site’s content on the edge node closest to each visitor. Pick a market to see the route.
Less waiting, smoother browsing for customers.
Speed comes from layer upon layer of detail: image compression, caching, CDN and leaner code. Click “Race again” to see which version finishes loading first.
From traffic and logins to backups, the right protection at every layer.
From the network to the login page, every layer has dedicated protection. Hover over the rings on the right to see what each layer does.
- SSL certificateSite-wide HTTPS with encrypted data in transit
- Malware scanningRegular scans of files and plugins for vulnerabilities
- Login protectionLimited login attempts, hidden admin path, two-factor authentication
- WAF (web application firewall)Rule-based detection and handling of malicious requests and abnormal traffic
- Network firewallBlocks unnecessary network access, with extra protection services assessed as needed
Keep working backups, ready for when you need to recover.
Backups run automatically to storage kept separate from your website, with multiple versions retained and regular test restores to confirm they actually work. Backup frequency and retention are agreed in the service agreement. Click a snapshot to see a demo restore.
Pick a snapshot, then click “Demo restore.”
Demo flow · Sample dates- Where it’s storedBackups use separate storage, not the server your website runs on, reducing the risk of both being hit at once.
- How long it’s keptMultiple versions are kept, so you can go back to before a problem appeared. Exact retention is agreed in the service agreement.
- Does it work?We regularly run a test restore from a backup to confirm it restores completely, instead of finding out a backup is broken when something goes wrong.
Automated 24/7 monitoring, with people responding as agreed.
Our monitoring system checks uptime, certificate expiry, disk space and unusual traffic around the clock, and sends email or chat alerts the moment something looks wrong. Once an issue is detected, an engineer takes over.
- 01 · AutomatedMonitor
Monitoring runs around the clock and alerts us the moment something looks wrong. This step needs no one on watch.
Runs automatically 24/7 - 02 · EngineerRespond
An engineer picks up the alert, confirms the issue, lets you know and starts working on it.
Response time agreed in the service agreement - 03 · Back onlineRecover
We fix the issue or roll back from a backup, the site is back to normal, and we explain the cause afterward.
Recovery targets agreed in the service agreement
Questions we often get before deployment.
Don’t see your question? Leave a message below. We reply within 1 business day.
$ faq --q 1Can the server be in my name?
Yes. We recommend buying the cloud server and domain with your own account, while we handle deployment and maintenance. Accounts are opened in your name, and all agreed deliverables are fully handed over.
$ faq --q 2Where should my server be located?
We choose the deployment based on where most of your visitors are, hosting conditions and maintenance requirements, and confirm any applicable access requirements before launch.
$ faq --q 3I already have a website. Can you move it to a new server?
Yes. We first set it up and fully test it on the new server, and agree the cutover window and rollback plan in advance to keep downtime to a minimum.
$ faq --q 4Do I need this on a SaaS platform like Shopify or Shoplazza?
On SaaS platforms the platform runs the servers, so you don’t need that part. For SaaS projects we can set up domains, email and tracking within what the platform supports; speed-related settings are assessed separately.
$ faq --q 5What if my site is attacked or goes down?
With a maintenance plan in place, any issue our monitoring detects is reported and handled right away, and we can restore from a backup snapshot if needed. Response times are agreed in the service plan.
$ faq --q 6How is it priced?
Costs mainly cover third-party fees such as cloud servers and CDN, plus our deployment and maintenance fees. We prepare a proposal based on your site’s size and needs; third-party fees are as published on each provider’s website.
Tell us about your business.
We’ll map out the next step.
Share where your business is and what you want to solve. We reply within 1 business day, then recommend the right services, scope and timeline.

