Agentic engineering infrastructure

Your project on a dedicated server

Move your Fractera node from a home computer to a dedicated server: the site runs around the clock, no longer depends on whether your computer is on, and stays yours.

  1. 01

    Always online

    A server answers even when your computer is off

  2. 02

    The same project

    Pages, sign-in and data move as they are

  3. 03

    Your domain

    The address belongs to you, not to us

You can deploy this project on a dedicated server so the site answers around the clock — even when your computer is off, rebooting or travelling with you. The code, the data and the domain stay yours: you rent the server, and nobody but you controls it. Back to Fractera.

What you get

  • A site that never sleeps. A home node runs while the computer runs; a server runs always.
  • The same project, no rework. The whole core moves — pages, sign-in, data and replaceable blocks.
  • Your domain, your rules. The address belongs to you, not to us: should Fractera disappear tomorrow, your site keeps working.
  • No subscriptions to other services. Sign-in, database and storage are already inside the project.
  • Regulatory compliance. Some regulators forbid routing traffic through Cloudflare. On your own server the site answers directly, with no intermediary, and that meets the requirement.
  • The certificate you choose. By default a free Let’s Encrypt certificate is issued and renewed automatically. If your regulator requires its own certificate, you can upload it.

How it works

  1. You rent an Ubuntu server from any provider.
  2. On the node’s internal page you enter the server address and start the installation. The project comes up on the server and first answers on its IP address over plain HTTP, so you can confirm the move worked before touching the domain.
  3. You point the domain at the server. The records that now send the domain and its sign-in subdomain into the tunnel on your computer are replaced with records carrying the server’s IP address. If your regulator forbids Cloudflare, the domain leaves Cloudflare entirely: the registrar gets its original name servers back and the tunnel is deleted.
  4. You switch on secure HTTPS: a Let’s Encrypt certificate is issued automatically, or you upload your own.
  5. The site runs under your domain over HTTPS, and it no longer needs your home computer to work.

The deployment form lives inside the node, in the architect layer: only the project owner can open it.