DocumentationGetting Started

Lofingo Cloud Overview

Understand the panel architecture, selected-server model, permissions, and the safest order for configuring a new VPS.

Panel route/dashboard

Lofingo Cloud is a standalone control panel for Ubuntu and Debian VPS machines. It combines server monitoring, file management, Git workflows, deployments, Nginx, domains, SSL, databases, mail, backups, object storage, Docker, and one-click applications in one authenticated dashboard.

How the panel is organized

The browser application sends authenticated requests to the Lofingo API. The API performs local server work through controlled helpers and can perform supported remote operations through the selected server connection. Nginx serves the dashboard and proxies API traffic to the private backend listener.

Dashboard and Metrics show server health, service state, diagnostics, and application-level observations.

Files and Git manage source trees, archives, uploads, editor tabs, repositories, branches, commits, and pull workflows.

Deployments turn a source directory into a managed service with commands, environment variables, ports, health checks, logs, and optional domain routing.

Domains, Proxy, and Nginx own public traffic, generated configuration, TLS certificates, revisions, and reverse-proxy routes.

Databases and Mail install and operate stateful services with users, permissions, backups, logs, and provider-specific checks.

Storage and Backups manage local object buckets, remote providers, API access, database backup jobs, retention, and restore artifacts.

Docker and Apps manage containers, Compose stacks, runtime packages, and full one-click services.

Selected server context

Most operational pages are scoped to the server selected in the panel. Confirm the active target before changing files, ports, services, domains, databases, or applications. A local target executes work on the panel host; a remote target must use the configured remote connection path supported by that feature.

Admin users can manage configured servers. Other users only receive the servers and operations granted to them. A hidden navigation item is not an authorization boundary: the backend still validates authentication, role, and server access.

Recommended first-run order

1.Sign in with the generated administrator credentials and change the password.

2.Configure the final panel URL and HTTPS before enabling integrations that depend on callback URLs.

3.Enable two-factor authentication and save recovery codes offline.

4.Verify the selected server, disk capacity, memory, CPU, time, and package state.

5.Open Apps and install only the runtimes or services required by the workload.

6.Add a domain, verify DNS, issue SSL, and then create the deployment or proxy route.

7.Configure backup storage and create at least one tested database backup job.

8.Review the port registry and notification preferences before exposing additional services.

Operational safety

Changes on these pages affect a real VPS. Read validation output before retrying an install or config change. Do not expose database, cache, broker, metrics, or administration ports publicly unless the network design requires it. Keep secrets in the panel's protected fields and never paste credentials into deployment logs, Git commits, or public Nginx files.