Static portal served by nginx
The public website is generated by Astro and served as static files from nginx:alpine.
About
A serious self-hosted platform with selected managed services
Layztr Cloud Systems is the formal public-facing name for a private self-hosted cloud and homelab environment operated by Fábio Furtado / Layztr. LayztrCloud is used as a shorter brand and domain reference.
The platform exists to organise private services, game servers, automation, storage and operational tooling through a clean static portal and a future protected dashboard.
It is also a small-scale managed services brand for selected clients: managed Minecraft servers, selected self-hosted application hosting and practical Linux/server administration.
The approach is sysadmin-oriented: containers, Linux maintenance, monitoring placeholders, Git-backed configuration placeholders and controlled service exposure. It does not present itself as a large hosting company or promise enterprise SLAs.
Platform
Infrastructure Overview
Layztr Cloud Systems is designed around self-hosted services, containerised workloads and controlled access. The portal itself is statically served and can later sit behind an external authentication or reverse proxy layer.
Docker / Docker Compose
The v1 deployment uses a simple Compose service exposing host port 8091 to container port 80.
Containerised services
Service entries describe practical containerised workloads and placeholders without exposing secrets.
Proxmox-based infrastructure placeholder
Virtualisation is represented as a protected admin service placeholder.
Git-backed configuration placeholder
Infrastructure and automation repositories can be represented through the Git service entry.
Monitoring placeholder
Status data is static for v1 and ready for future monitoring integration.
Storage/NAS/DAS placeholder
Storage services are described at a high level without inventing private infrastructure details.
Future external authentication
Azure Entra ID App Registration can later be used through an external OIDC-capable access layer.
Security model
Access Is Deliberate
The app is a static portal. It labels private areas clearly, but those labels are informational until an external authentication layer is added.
- Public landing pages are open and indexable.
- Dashboard and admin areas are intended to be private/protected.
- v1 does not enforce authentication inside the Astro app.
- Authentication should be handled externally before exposing private routes publicly.
- Azure Entra ID App Registration is a planned identity provider option through an external gateway.
- Admin services should not be exposed directly to the internet.
- No secrets should be stored in the frontend.
- TLS and authentication should be handled by the external access layer when deployed publicly.
- Client/private service links should not be exposed unless intentionally configured.
Future Authentication Model
Azure Entra ID App Registration may be used later as an identity provider through an external OIDC-capable gateway. The Astro app does not include Azure SDKs, MSAL, OAuth callback routes, sessions, token handling or secrets.
Service request
Need a managed server or self-hosted service?
Layztr Cloud Systems can support selected small-scale hosting and infrastructure setups, including Minecraft servers, self-hosted applications, monitoring and Linux service maintenance.
No backend contact form is included in v1. Update the mailto link when you are ready.