Start with a finished page
18 complete pages built from LightPane panes. Open one to see it working on example data, then download the HTML, CSS and key loader and host it yourself — they are yours to edit.
No account needed to look. Every preview here runs on example data, clearly marked, so you can judge the layout before you connect anything. Add your own access key to the copy you download and the same page reads your estate. Want to see panes against a real cloud instead? That is what the demos are for.
Full overview
One page per cloud, everything on it. The widest view, and the usual place to start.
Amazon Web Services overview
Region footprint, daily briefing, security findings, right-sizing, cost and free-tier monitors across five sections.
Azure · 16 panesMicrosoft Azure overview
Subscription-wide footprint, change feed, security findings, identity audit and cost, grouped the same way.
GCP · 16 panesGoogle Cloud overview
Project footprint, change feed, security findings, identity audit and cost, grouped the same way.
By use case
Narrower, and sharper for it: one question per page.
AWS cost & free tier
Spend, forecast and cost by tag, then the waste: right-sizing, idle resources, reservations — and what is still inside the free tier.
Azure · 6 panesAzure cost & free tier
Spend, forecast and cost by label, with right-sizing and idle resources.
GCP · 6 panesGCP cost & free tier
Spend, forecast and cost by label, with right-sizing and idle resources.
AWS · 10 panesAWS security posture
Findings, Security Hub and GuardDuty, then exposure, identity and key rotation — the security half of the overview, on one page.
Azure · 5 panesAzure security posture
Findings, public and network exposure, identity audit and key rotation.
GCP · 5 panesGCP security posture
Findings, public and network exposure, identity audit and key rotation.
By architecture
Shaped around a way of building rather than a cloud.
Migration
Before, during and across — two accounts or two clouds, side by side.
Migration planning
Footprint, inventory, spend and idle resources for AWS, Azure and Google Cloud on provider tabs — what you have, before you decide what moves.
Multi-cloud · 22 panesMigration tracking — two AWS accounts
Source and target side by side while the move runs in both: network, compute, data, footprint, spend and readiness, each asked of both accounts at the same moment.
Multi-cloud · 16 panesMigration tracking — AWS to Google Cloud
The same side-by-side layout across two providers, each read with its own credentials — including where the equivalents do not map neatly.
Multi-cloud
The same question asked of every cloud at once.
Documents, not dashboards
Pages that read as a written answer, with the evidence live underneath — for people who will never log in to a cloud console.
Incident triage
A first-response checklist: is it AWS or us, is it load, did something change, have we hit a limit, is it an attack — each question answered on the page, for responders with no AWS login.
AWS · DocumentProduction readiness check
The pre-release questions answered from the live account — health, recoverability, drift, headroom, expiry and exposure — so the sign-off is evidence rather than recollection.
AWS · DocumentNew starter: estate walkthrough
Where we run, what runs there, how traffic gets in, where the data is, who can get in and what it costs — an orientation anyone can read without an AWS login.
AWS · DocumentS3 security controls
Control wording with the evidence for it directly underneath, read live from the account — so the control owner, the application owner and the auditor are all looking at the same thing.
Then what
A template is a starting point, not a ceiling. When you want to change the layout or build your own page, Putting panes on a page explains the DOM contract these files use, and the pane catalog lists every pane you can drop into one.