sudievu

© 2026 Justas Vaičekauskas

info@sudievu.lt +370 656 94057

LT
Menu

Hosting

Hosting with a control panel

Your site on my server in Lithuania. The panel shows whether it is up, when the last backup was made and how much room is left. Whether or not I built the site.

Hosting costs from €10 a month for a site I built and from €15 for a site someone else built. Plans and prices are on the pricing page.

At the same moment I get an email: vetrungesnamas.lt is down.

No password: just your email address.You type the address and press.An email arrives with a one-time link that lasts 15 minutes.The link opens a confirmation: one press.And you are in.The first sentence says whether the site is up. It is checked every 5 minutes.Uptime over 30 days, speed, certificate, domain, the last backup.Your plan, and how to reach me.An ordinary day.The site is down: the page says so at once, and since when. I get an email.Once it is fixed, the page is calm again.On a phone, the links are in the menu.Files: the site’s folder, right in the browser.You see your own site’s files and nothing else.You open a file……change it and save.Saved. If the site is published from your own file storage (Git), the panel warns that the next publish will overwrite this change.An encrypted backup every night; the server keeps the last 7 nights, the copies elsewhere 30 days.Pick a night and what to restore: files, a database or the whole site.Before anything is restored, it tells you what will happen.Restoring: the backup is read, checked, then swapped in.Restored. What was there before stays in a restore point for 14 days: it can be undone.Staging: a place for changes your visitors do not see yet.One press makes a copy of the site.The files and the database are copied.The copy runs at its own address. When you like it, you publish it, and that can be undone.Your site’s files stay in your own file storage (GitHub or GitLab).You enter the storage’s address; the panel makes a key that can only read.You add the key to the storage; the panel checks it can reach it.You save.You confirm the site will be published from this storage.The site is built and published.Published. From now on every change you upload to the storage is on the site in about a minute.No account yet? You sign up.An email address and a name.An email arrives with a link to confirm.One press, and the account exists.You choose a plan and a domain.You fill in your details and accept the terms.The order waits for me to approve it.Once approved, the panel shows each step: the site, the certificate, the email.The site is ready, and the panel already shows it.Help in plain words, open even when signed out.Type a word and find where it is explained.On a phone, the language is in the menu.The whole panel in Lithuanian and English.One press.My side: the whole server and every site in one place.Each site’s response time, certificate and domain.What happened: publishes, updates, outages.

The real panel with invented data: the example site “Vėtrungės namas”.

How it all fits together

The start is the same, then you take one of two ways: you host it yourself, or I host it for you. Both end on the same server with the same care, and the panel shows you what is going on.

  1. The start

    Everyone begins the same way

    1. 1You
      Sign up and order

      You sign in with an email link, no password, and order a plan: an address like name.sudievu.lt, or your own domain.

    2. 2Me
      I approve the order

      One click. Only then is the site made, automatically: its own place on the server, a secure address (https) and backups. The first invoice comes when the site is ready.

  2. First way

    You host it yourself

    Your site’s files stay in your own file storage (GitHub or GitLab), and you keep working as you do now. It needs a plan that includes publishing from the storage (Git).

    1. 3You
      Connect your file storage

      In the panel you connect it once, with a key that can only read.

    2. 4You
      Upload your changes

      You upload your changes to the storage. You can also upload files in the panel’s file manager or with a file-transfer program (SFTP).

    3. 5Automatic
      The site is published

      After every upload the site is published and is live in about a minute. If the site must first be prepared from its source files (Astro, Vite or Hugo), that happens automatically; a ready-made PHP or HTML site is published as it is.

      How I update my own sites: checked first
  3. Second way

    I host it for you

    You need no technical tools. It does not matter whether I built the site.

    1. 3Me
      I put the site up

      One I built, or one moved from elsewhere. I set up the domain. Mailboxes are not part of hosting.

    2. 4Me
      I keep it running

      I make sure the site runs and stays up to date.

    3. 5You
      You watch in the panel

      You see what is going on in the panel, and ask questions through it.

  4. The server in Lithuania

    My own server. The sites from both ways run here.

  5. Checked every 5 minutes

    For each site: is it up, is the certificate valid, when does the domain expire, how much disk is left.

  6. Alert by email

    If something is wrong, I get an email at once. It is not sent to the client.

  7. The panel

    What the server checked, in the panel: whether the site is up, certificate and domain expiry, backups, disk space.

  8. Nightly backup

    Every night an encrypted copy of the sites leaves the server.

    How the copy is made
  9. A second place

    The copy is kept elsewhere, not on the same server, so it is not lost together with it.

    The three places the copies are kept
  10. Restore

    From the panel you restore files, a whole site or a database from a copy. A restore can be undone.

    Restores, and the restore drill
  11. Staging site

    Try changes on a copy of the site at name-staging, then publish them to the live site. A publish can be undone.

What is included

What you see

  • Whether the site is up: checked every 5 minutes, a failure checked again a minute later.
  • Uptime over 30 days, outages and how long they lasted.
  • Days left on the secure-connection certificate and the domain.
  • The last backup, how long backups are kept, a copy kept elsewhere.
  • Space used, traffic per month, when the software was last updated.
  • A history of events: 90 days.
  • A file manager in the site’s folder, and password-protected folders.
  • Restoring from the night you choose, with an undo kept for 14 days.
  • Lithuanian and English.

What I do

  • An encrypted backup every night: databases, files, settings. 7 days on the server, 30 on my computer and in one more place.
  • Restore drills: sites rebuilt from the backup and checked.
  • Certificates renewed automatically; security updates install themselves.
  • The server is protected: a firewall, key-only sign-in, and addresses that attack are blocked automatically.
  • Each site is kept apart from the others on the server.
  • When a site is down or a backup is late, I get an email.

Signing in

  • No passwords: a one-time link by email, valid for 15 minutes.
  • If you like, a second step with a code from an app.
  • You see only your own sites. No visitor addresses anywhere in the panel.

The server is my own, in Lithuania; a standby copy is kept in Interneto vizija’s data centre in Vilnius.

Technical detail

The server is reached through Cloudflare’s network. Ubuntu 24.04, PHP 8.3; each site runs as its own Linux user.

Try it yourself

The same panel you would get with your site, filled with invented data and running in your browser: sign in, change a file, restore a night, cause an incident. Nothing leaves your computer.

Open the panelThe real panel’s help

Want to host with me?

Tell me about your site and where it is now. I will answer with what I can offer and at what price.

You will hear back within one working day.

The site’s address, where it is hosted now, and whether I built it.

What you type goes to that address and nowhere else.