Questions and answers

PodiCloud is hosting for projects with dedicated resources. Each project runs in its own container, and the processor, memory and disk of its plan are not shared with neighbours — just like on a VDS. Yet there is no server to set up: domains, certificates, databases, backups and updates are handled by the control panel.

A project is a single website, bot, API or service with its own files, domains, databases, cron jobs and backup copies. A project has its own plan, that is, its own guaranteed resources. You can have as many projects as you like, and they do not interfere with one another.

1. Sign in to the control panel and top up your balance.
2. Choose a plan on the “Plans” page or build your own in the configurator.
3. The wizard asks what to run (PHP, Node.js, Python, Go or your own image) and where to host the project.
4. Upload your code and link a domain — the certificate is issued automatically.

PHP and static websites, Node.js, Python and Go applications, a ready-made executable, and your own Docker image — from a registry or built from the project's Dockerfile. You choose the version of PHP, Node.js, Python and Go when creating the project and can change it later. The set of available options depends on the plan.

Yes. Each project needs its own plan: the resources of one project are not consumed by others. All projects, databases and backup copies are visible in a single panel.

You top up the balance in the panel, and the price of the plan is debited from it once a month: when you order and then at the start of each following period. Auto-renewal is enabled by default; you can turn it off on the “Plans” → “My plans” page.

In the panel, open “Finance” → “Top up the balance”. The available payment methods are shown there. The money is credited as soon as the payment is confirmed; the transaction history is visible under “Finance”.

The panel reminds you about the renewal in advance by email and with a notification. If there is not enough money on the balance, the project is suspended and its data is kept for a while longer — the exact periods are stated in the public offer and on the project card. After payment the project starts again. If it is not paid for by the end of the retention period, the project and its backup copies are deleted permanently.

“Plans” → “My plans” → “Upgrade plan”. The extra charge is calculated for the remaining part of the paid month, the project gets the new resources immediately and nothing has to be moved. Downgrading a plan is not possible: it could lead to data loss.

A plan where you set the processor, memory, disk and number of databases yourself, and the price is calculated from the resources you choose. The resources can be changed later in the panel — in either direction, except the disk, which can only be increased.

The unused remainder of the money on your balance is refunded at your request — the terms and timing are described in the public offer. Payment for a month that has already begun and bonus funds are not refunded.

In three ways: over SFTP (the address, port and login are shown on the project card), through the file manager in the panel, or by deploying from git. For teamwork you can create additional SFTP accounts with access to a particular folder only.

On the project card, find the “Git deploy” block and enter the repository address and the branch. The panel shows a deploy key — add it to the repository as a read-only key. A deployment is started with a button or by a webhook: the panel fetches the code, runs the build command and restarts the project.

Enter the build command in the handler settings, for example npm ci && npm run build or composer install, and click “Build”. The command runs inside the project's container. One-off commands are easiest to run in the project's terminal.

Yes. On the “Manage” tab you set up scheduled jobs in the usual cron format and background processes that the panel keeps running — a queue worker, for example. How many you can have depends on the plan.

The project card has the “Logs” and “Terminal” tabs. The logs show the application's output and the requests; the terminal opens a command line inside the project's container.

Yes, if the plan includes ports. On the project card, add your application's port — the panel issues an external port through which it is reachable from the internet (TCP or UDP). Ordinary websites do not need ports: web requests arrive via the domain.

In the project's environment variables: the “Manage” tab → “Environment variables”. They are stored encrypted in the panel and passed to the application when it starts, instead of sitting in the project's files.

At your domain registrar, create an A record pointing to the address shown on the project card. Then open “Domain and TLS” in the project and add the domain. A Let's Encrypt certificate is issued within a couple of minutes and renews itself.

Yes. Your own certificate is uploaded in the “Certificates” section and selected for the domain. If the domain is proxied through Cloudflare, mark this on the domain and use a Cloudflare Origin CA certificate.

A domain has its settings: the address with www can be redirected to the one without www or the other way round, and HTTP requests can be forced over to HTTPS.

In the “Databases” section, select the project and click “Create”: MariaDB and PostgreSQL are available. The panel creates the database and a user with a password; the address and port for connecting are shown there too. Users can be given read-only or full access, and the addresses allowed to connect can be restricted.

Yes, for MariaDB databases: the “phpMyAdmin” button next to a database opens it straight in that database, with no password to enter.

A database has the “Download a dump” and “Upload a dump” buttons. A large dump is easier to upload to the project's files over SFTP and import from there — that way it does not depend on the browser's limits.

A backup copy includes the project's files, its databases and its settings: the handler, environment variables, domains, ports, cron jobs, processes, SFTP accounts and database users. By default a copy is taken once a day; the time and the number of copies kept can be adjusted within the limits of the plan. Copies take up the project's disk space.

In the “Backups” section, click “Restore” next to the copy you need and choose what to bring back: files, databases, settings. The project is stopped while it is being restored and then starts again by itself.

Download the archive of the backup copy and click “Restore from an archive” in the “Backups” section. The panel shows the contents of the archive and offers to create a new project from it on a plan that is not yet in use, or to restore it into an existing project — together with the settings, if they fit within the plan.

Yes. In the “Backups” section you can connect external storage: S3-compatible, SFTP, WebDAV or Google Drive. Copies are sent there encrypted with your key — keep it somewhere safe. We also recommend keeping important data on your own side.

In your profile, enable signing in with a code from an authenticator app (two-factor protection) or add a passkey — a fingerprint, Face ID, Windows Hello or a hardware key. All sign-ins and actions are recorded in a log that you can see in your profile.

No. Projects run in separate containers with their own file system and network, and only the users you have created can connect to the databases.

Check your login and keyboard layout and, if two-factor protection is enabled, the time on your phone. If you still cannot sign in, write to [LANDING_SUPPORT_EMAIL] from the address stated in your account.

In the panel, open “Support” and create a ticket: that way we see straight away which account and project it concerns. If you cannot sign in to the panel, write to [LANDING_SUPPORT_EMAIL].

The project, what exactly happened and when, what you expected to see and what you have already tried. The error text, a screenshot or lines from the logs save time for both sides.

We are responsible for the operation of the service: the panel, containers, domains and certificates, databases, backups, payments. Developing and debugging your application's code remains up to you, but we will point you to where to look for the cause on the service side.