# CloudQube docs > Set up domains, email, databases, containers, analytics, and more on CloudQube. EU-hosted, pay-per-use. --- ## CloudQube docs Source: https://docs.cloudqube.eu/ Set up domains, email, websites, analytics, and more on CloudQube. EU-hosted, pay-per-use. CloudQube docs Spin up the parts of your project. Everything you need, in one place, hosted in the EU. Set up your first project Browse the guides Pick a path Section titled “Pick a path” New here? Walk through your first project with the wizard. Five minutes, no coding, real infrastructure at the end. Start the walkthrough Building something specific? Jump into a how-to: register a domain, send your first email, publish your site. Browse guides Want the API? Authenticated endpoints, webhooks, rate limits, error codes. API reference Curious how it works? The mental model: qubes, projects, pay-per-use, EU residency. Read the concepts What CloudQube is Section titled “What CloudQube is” CloudQube is a single account where you set up the resources a small project needs: a domain, email, a website, analytics, monitoring. We connect to managed providers in the EU on your behalf, take care of the wiring, and bill you only for what you use. What CloudQube is not Section titled “What CloudQube is not” We do not run servers for you. We do not lock your data inside our platform. Every resource we set up belongs to your project; you can export it or take it elsewhere whenever you want. Last updated: Jul 21, 2026 --- ## Welcome Source: https://docs.cloudqube.eu/start/ Pick a path to set up your first project on CloudQube. Welcome Coming soon. Last updated: Jul 3, 2026 Next Your first project --- ## Your first project Source: https://docs.cloudqube.eu/start/first-project/ Spin up a real project in five minutes using the wizard. No coding required. Your first project By the end of this walkthrough you will have: A registered domain you own. DNS pointed to your project, with DNSSEC turned on. An email address you can send and receive from on that domain. A first VAT-compliant invoice in your inbox. Total time: about five minutes. You will need a payment method (card, iDEAL, or SEPA) to pay for the domain registration. Create your account Go to app.cloudqube.eu and sign up. We use email + a one-time code, no password to remember. Pick a project name The first thing the wizard asks for is what you are building. “My SaaS startup”, “Family recipe blog”, whatever fits. This is internal-only; nobody outside your account sees it. Search for a domain Type the name you want. The wizard checks availability across the common endings (.eu, .com, .nl, .be, .de) and shows you the price for each. Tip Pick a .eu if you want EU-jurisdiction registration; pick a .com if you want global recognition. They cost about the same. Choose your starter template (or skip) Templates bundle a domain with the qubes that usually go alongside it. The “portfolio” template adds a hosted site, analytics, and monitoring. The “domain + email” template just adds DNS and email. You can also skip and add qubes one at a time later. Confirm and pay The wizard shows the breakdown: the domain registration cost, plus a transparent CloudQube margin, plus VAT for your country. Confirm to pay through your chosen method. Wait for setup The wizard shows a progress bar as each qube is set up. Domain registration takes 30 to 90 seconds. DNS turns on with DNSSEC right away. The email qube needs DNS records to propagate before it is ready, usually a couple of minutes. You are done You land on the project dashboard. From here you can send a test email, browse to your domain, or add more qubes. Your invoice is already in your inbox. What happens next Section titled “What happens next” You receive a welcome email confirming your project is live, with links to manage each qube. You receive an invoice email with the VAT-compliant PDF attached. You can edit anything from the dashboard, including the project name, the team members with access, and the qubes themselves. Common questions Section titled “Common questions” Do I need to add a payment method up front? For one-shot purchases like a domain registration, yes. For recurring resources you set up later, you Pay at checkout; the exact price is confirmed first. What if something goes wrong? The dashboard shows the status of every qube and surfaces any error in plain English with a suggested next step. If you are stuck, the support email is in the footer of every page. Last updated: Jul 21, 2026 Previous Welcome Next Projects and templates --- ## Your first invoice Source: https://docs.cloudqube.eu/start/your-first-invoice/ What CloudQube invoicing looks like end to end. Your first invoice Coming soon. Last updated: Jul 3, 2026 Previous VAT invoicing Next Export your data --- ## Leaving CloudQube Source: https://docs.cloudqube.eu/guides/account/leaving-cloudqube/ Take your data and domains with you, then close your account. Leaving CloudQube There’s no lock-in. If you decide to leave, take what’s yours first, then close your account. Export your data. Download your account data (profile, projects, invoices, and more). See Export your data . Move any domains you want to keep. Transfer them out to another registrar before you close your account. We give you the authorization code and unlock the domain. Delete your account from Account → Data . Deletion is immediate Deleting your account decommissions the services we provisioned for you (sites, email, DNS) and erases your data straight away, with no grace period. Export anything you want to keep, and move out any domains, first . Domains are the one thing that isn’t destroyed on deletion (cancelling a live domain is usually the wrong thing to do), so transfer out any you want to keep before you go. Last updated: Jul 21, 2026 Previous Two-factor authentication Next Domain not resolving --- ## Two-factor authentication Source: https://docs.cloudqube.eu/guides/account/two-factor-authentication/ Add a second step to your login for extra account security. Two-factor authentication Two-factor authentication (2FA) adds a second step to your login: after your password, you enter a rotating code from an authenticator app on your phone. Even if someone learns your password, they can’t sign in without your phone. Turn it on Section titled “Turn it on” Go to Account → Security and start setting up 2FA. Scan the QR code with an authenticator app (Google Authenticator, 1Password, Authy, or similar). Enter the 6-digit code the app shows to confirm, and it’s on. From then on, you’ll enter a code from your app each time you sign in. Keep a way back in Store your authenticator setup somewhere safe (many apps let you back it up). If you lose access to your authenticator, contact support to recover your account. Last updated: Jul 3, 2026 Previous Export your data Next Leaving CloudQube --- ## Add tracking to your site Source: https://docs.cloudqube.eu/guides/analytics/add-tracking-to-your-site/ Drop the tracking snippet into your site or app. Add tracking to your site Coming soon. Last updated: Jul 3, 2026 Previous Deploy a static website Next Share a public dashboard --- ## Share a public dashboard Source: https://docs.cloudqube.eu/guides/analytics/share-a-public-dashboard/ Make your analytics dashboard public for stakeholders. Share a public dashboard Coming soon. Last updated: Jul 3, 2026 Previous Add tracking to your site Next Uptime monitoring --- ## Export your data Source: https://docs.cloudqube.eu/guides/billing/export-your-data/ Download all invoices, contacts, and project data. Export your data Coming soon. Last updated: Jul 3, 2026 Previous Your first invoice Next Two-factor authentication --- ## How billing works Source: https://docs.cloudqube.eu/guides/billing/how-pay-per-use-works/ One monthly plan for running services, one-off checkout for domains, VAT invoices for everything. How billing works CloudQube charges on two tracks. Track 1: your monthly plan Section titled “Track 1: your monthly plan” When you pick a paid plan you pay the first month at checkout; that payment also saves your payment method for renewals. Each month, on your plan anniversary, the total of your base plan plus add-ons is charged automatically. You get a pre-notification email two days before every charge, and a VAT invoice for every payment. Changing add-ons is instant: adding one charges only the prorated remainder of your current month; removing one takes effect at the next renewal, so you always keep what you paid for. Track 2: one-off purchases Section titled “Track 2: one-off purchases” Domain registrations, transfers, and renewals are single payments at checkout, priced per name and confirmed before you pay. If a purchase can’t be completed after you’ve paid (for example the name was taken in the meantime), the payment is refunded automatically and you get a credit note. If a plan payment fails Section titled “If a plan payment fails” Nothing breaks immediately: everything keeps working while we retry over the next two weeks and email you each time. If payment can’t be collected by then, the plan ends and your account drops to the free tier. What you can never get Section titled “What you can never get” An overage bill. Fair-use caps pause a service; they never charge extra. A subscription you can’t leave. Cancel any time; the plan runs out at the end of the paid month. A hidden markup on domains. The price you see at search is the price you pay. Last updated: Jul 21, 2026 Previous Connect Mollie Next VAT invoicing --- ## VAT invoicing Source: https://docs.cloudqube.eu/guides/billing/vat-invoicing/ How CloudQube handles VAT, where invoices come from, and how to keep your VAT number on file. VAT invoicing CloudQube generates a VAT-compliant invoice for every charge: A one-shot purchase (e.g. a domain registration) gets an invoice the moment the payment succeeds. A daily deduction from your monthly plan charge gets its own invoice at payment time. A top-up of your prepaid balance gets a payment receipt; the invoice for the matching consumption is emitted with the consolidated monthly run. Every invoice is emailed to you and is also available in your account settings. What VAT regime applies Section titled “What VAT regime applies” The qube picks the regime automatically based on your account’s billing country and VAT status: Your situation Regime What you see on the invoice Consumer in the Netherlands Domestic NL VAT NL VAT line at the standard rate Consumer in another EU country OSS (One Stop Shop) Your country’s VAT rate, declared by us under OSS Business in another EU country with a valid VAT number Reverse charge No VAT line; “BTW verlegd” / “VAT reverse charged” notice Customer outside the EU Export No VAT line If your VAT number changes, update it in your account settings before your next invoice. Updates do not retroactively re-issue past invoices; we issue a credit note + corrected invoice if needed. Caution Reverse charge requires a valid EU VAT number that we re-validate against VIES every time we issue an invoice. If VIES says your number is invalid at invoice time, the invoice is issued with VAT and you can claim a refund through your local tax authority. What is on every invoice Section titled “What is on every invoice” Your billing details (name, address, country, VAT number if applicable). Our billing details (CloudQube, NL incorporation, NL VAT number, KVK number). A unique sequential invoice number. The date. One line per charge: description, quantity, unit price, line total. The VAT regime applied and the calculated VAT line if any. The total in euros. Payment status (paid, refunded, etc.). Refunds and credit notes Section titled “Refunds and credit notes” We do not delete or amend issued invoices, ever (legally we cannot). If a charge is refunded, we issue a credit note that references the original invoice number and zeros out the original amount. Both stay on file. Where to find them Section titled “Where to find them” Email : every invoice is sent to your billing email when issued. Account settings → Billing → Invoices : full history, downloadable as PDFs. Account settings → Export your data : a single ZIP with every invoice plus a CSV index. See Export your data . Retention Section titled “Retention” Invoices are retained for 10 years per Dutch tax law. You can download them at any point. Last updated: Jul 21, 2026 Previous How billing works Next Your first invoice --- ## Register a domain Source: https://docs.cloudqube.eu/guides/domains/register/ Register a new domain through CloudQube. Includes DNS and DNSSEC, set up automatically. Register a domain Registering a domain through CloudQube includes: The domain registration itself, with the appropriate registry. DNS hosting, included free, no separate setup. DNSSEC turned on automatically, signed and verified end to end. Auto-renewal opt-in, with renewal price visible up front. Open the domain qube From your project dashboard, click Add qube and pick Domain , or open the existing Domain qube if you already have one on this project. Search Type the name you want without an extension. The qube checks the common endings and shows you the wholesale price plus the CloudQube margin and VAT for your country. Pick an extension Each extension has a different price. The qube shows the total cost for the first year and the renewal cost for the next year so you know what to expect. Confirm The price you see is the price you pay. Click Register to pay and queue the registration. Wait for the registry Most registrations come back within 30 seconds. Some endings ( .eu , .de ) can take up to 90 seconds. The qube polls in the background and updates the dashboard when the domain is live. What you get automatically Section titled “What you get automatically” DNS hosting is provisioned in the same step. You do not need to add a separate DNS qube; the domain qube takes care of it. DNSSEC is signed and the DS record is published to the registry without action from you. The dashboard shows a green chain-of-trust indicator once the registry has acknowledged it. A welcome record set : an apex A / AAAA placeholder, a MX set if you also added an email qube, and SPF/DKIM/DMARC if you also added an email qube. Renewal Section titled “Renewal” By default, auto-renew is on. The renewal price is the same as you saw at registration, plus VAT. You receive an email 30 days before renewal and an invoice the day the renewal succeeds. To turn auto-renew off, open the domain in the dashboard and toggle Auto-renew . Domains that are not auto-renewed expire and are released back to the registry at the end of the registration period. Caution If your domain is registered for an unusually high price (a “premium” domain), CloudQube may cap the renewal automatically until you confirm. You will get an email asking you to confirm the renewal price. What if my domain is taken? Section titled “What if my domain is taken?” The qube suggests close alternatives that are available, with prices. If you really want a domain that is registered to someone else, you can: Check WHOIS to see who owns it (the domain qube has a button for this). Place an inquiry through a marketplace (links offered in the qube). Wait. Domains released by their current owner show up in the qube’s “available again” feed. Last updated: Jul 3, 2026 Previous Your data & privacy Next Transfer a domain in --- ## Transfer a domain in Source: https://docs.cloudqube.eu/guides/domains/transfer-in/ Move a domain you already own at another registrar into CloudQube. Transfer a domain in If you already own a domain at another registrar, you can move its registration into CloudQube. Once the transfer completes it becomes a fully managed domain here, the same as one you registered with us: DNS, DNSSEC and renewals are handled for you. Before you start Section titled “Before you start” Unlock the domain at your current registrar (turn off the registrar / transfer lock). Get the authorization code (also called the EPP code, auth code, or transfer key) from your current registrar. The domain must be more than 60 days old . ICANN blocks transfers for the first 60 days after a registration or a previous transfer. Start the transfer Section titled “Start the transfer” Go to Account → Domains and choose Transfer a domain in . Enter the domain and its authorization code , and confirm the contact details (we pre-fill these from your saved registrant contact where we can). Confirm. The transfer fee is charged from your balance straight away. If your balance is short, you can top up first. What you pay, and when The transfer fee (which includes one year of renewal) is charged when the transfer starts. If the transfer does not complete, that amount is refunded to your balance automatically. While it’s in progress Section titled “While it’s in progress” A transfer usually takes 5 to 7 days , driven by your losing registrar and the registry, not by us. The domain shows a Transferring in badge on the Domains page during this time. You don’t need to do anything unless your current registrar emails you to approve the transfer. When it completes, the domain flips to Verified and its management controls (auto-renew, DNS, transfer-out) appear. If it’s rejected or times out, you’ll see a Transfer failed badge and the fee is refunded. Common reasons a transfer fails Section titled “Common reasons a transfer fails” The domain was locked at the current registrar. The authorization code was wrong or expired. The domain is inside the 60-day post-registration lock. The admin contact email at the current registrar didn’t approve the transfer. Fix the cause and start the transfer again; a failed attempt is refunded, so you’re never charged twice. Last updated: Jul 3, 2026 Previous Register a domain Next Transfer a domain out --- ## Transfer a domain out Source: https://docs.cloudqube.eu/guides/domains/transfer-out/ Move a domain from CloudQube to another registrar. Your domain, your choice. Transfer a domain out A domain you register or transfer into CloudQube is yours. You can move it to another registrar whenever you like. We give you everything the new registrar needs: the authorization (EPP) code and an unlocked domain. Get your transfer details Section titled “Get your transfer details” Go to Account → Domains and find the domain. Choose Transfer to another registrar . This reveals the authorization (EPP) code and shows whether the domain is currently locked. If it’s locked, choose Unlock for transfer . Start the transfer at your new registrar Section titled “Start the transfer at your new registrar” At the registrar you’re moving to, start an inbound transfer , enter your domain, and paste the authorization code . Approve the transfer email that’s sent to your registrant contact, and pay their transfer fee (a transfer usually includes one year of renewal). 60-day lock ICANN blocks any transfer for the first 60 days after a domain is registered or after a previous transfer. If your domain is inside that window, the Domains page shows the date it becomes transferable. What happens to your services Section titled “What happens to your services” Your services on CloudQube keep working until you move the domain’s nameservers at the new registrar. Move them when you’re ready to point the domain elsewhere. If you’re leaving CloudQube entirely, see Leaving CloudQube . Last updated: Jul 3, 2026 Previous Transfer a domain in Next Send your first email --- ## Compose and schedule email Source: https://docs.cloudqube.eu/guides/email/compose-and-schedule/ Write email in the dashboard, undo a send, or schedule it for later. Compose and schedule email Open the email qube on your project and click Compose . The composer supports To, CC, and BCC (up to 25 recipients per email in total), rich-text formatting, attachments (up to 10 MB per email), and an optional signature that is appended automatically. A recipient and a subject are always required. Sending now Section titled “Sending now” Send doesn’t fire immediately: the email waits 15 seconds with an Undo button. Undo reopens the composer with your message intact. Sending later Section titled “Sending later” Next to Send, open Send later and pick a date and time (shown in your local timezone). The email can be scheduled up to 30 days ahead and goes out within a minute of the chosen time. What you schedule is frozen: the message that goes out is exactly what you confirmed, even if you keep drafting other emails afterwards. Viewing and cancelling scheduled emails Section titled “Viewing and cancelling scheduled emails” Scheduled emails stay in the Drafts list with a badge showing when they will send. Use the cancel action on the draft to stop the send; the email reverts to a plain draft. Opening a scheduled email cancels it Opening or editing a scheduled draft cancels its schedule, so you can never accidentally change an email that’s about to go out. After editing, confirm Send later again to reschedule it. If sending is blocked at the scheduled time Section titled “If sending is blocked at the scheduled time” Conditions like a sending limit or a domain still finishing setup are checked at send time, not at scheduling time. If the send can’t go out yet, it retries for up to 24 hours; after that the draft is marked failed with the reason shown on it, and you can fix the issue and reschedule. Last updated: Jul 19, 2026 Previous Send your first email Next Staying out of spam --- ## Staying out of spam Source: https://docs.cloudqube.eu/guides/email/deliverability/ How CloudQube authenticates your email, and habits that keep you in the inbox. Staying out of spam Landing in the inbox is part authentication (which CloudQube handles for you) and part sending habits (which are up to you). What we set up for you Section titled “What we set up for you” When you set up email on your domain, CloudQube publishes the DNS records that mailbox providers check to confirm your mail is genuine: SPF , DKIM , and DMARC . You don’t configure these yourself; they’re added to your domain automatically. Habits that keep you in the inbox Section titled “Habits that keep you in the inbox” Only email people who expect to hear from you. Sending to addresses that never opted in is the fastest way to the spam folder. Use a consistent, real from-name and address on your own domain. Watch bounces and complaints. Keep removing addresses that bounce or unsubscribe. See Handle bounces . Warm up gradually. If you’re new to sending, build volume over days rather than blasting a large list on day one. Write like a person, not a billboard. Heavy images, lots of links, and spammy words all hurt. Already in spam? If messages are being filtered, see Email going to spam . Last updated: Jul 3, 2026 Previous Compose and schedule email Next Handle bounces --- ## Handle bounces Source: https://docs.cloudqube.eu/guides/email/handle-bounces/ Read your suppression list and resubscribe addresses. Handle bounces Coming soon. Last updated: Jul 3, 2026 Previous Staying out of spam Next Deploy a static website --- ## Send your first email Source: https://docs.cloudqube.eu/guides/email/send-your-first-email/ Set up the email qube on a domain and send your first email from the dashboard. Send your first email By the end of this guide you will: Have an email qube set up on one of your domains. Have SPF, DKIM, and DMARC records published in DNS automatically. Have sent a real email from the dashboard and seen it arrive. Add the email qube From your project dashboard, click Add qube and pick Email . Choose the domain you want to send from. The qube needs DNS to be managed by CloudQube so it can publish the SPF/DKIM/DMARC records itself. Wait for setup to finish The qube publishes the DNS records and verifies them. Typically this takes a few minutes. While verification is pending, sending is blocked and the composer tells you the domain is still being set up; once it clears, you’re ready to send. Compose and send Open the email qube and click Compose . Fill in a recipient and a subject (both are required), write your message, and hit Send . You get a 15-second undo window before the email actually goes out. Check your inbox The email arrives within seconds. If it lands in spam, see Email going to spam . Not at your desk when it should go out? You can schedule an email up to 30 days ahead with Send later . See Compose and schedule email . Receiving email Section titled “Receiving email” The same qube also receives email on your domain: incoming messages appear in the inbox on the qube’s dashboard, and you can reply from there. What happens to bounces Section titled “What happens to bounces” Bounces are tracked automatically and added to your suppression list so you don’t keep sending to dead addresses. See Handle bounces . Last updated: Jul 19, 2026 Previous Transfer a domain out Next Compose and schedule email --- ## Uptime monitoring Source: https://docs.cloudqube.eu/guides/monitoring/uptime-checks/ Get notified when one of your services stops responding. Uptime monitoring Uptime monitoring watches a URL and tells you when it stops responding or gets slow, so you find out before your visitors do. Any public URL works: the site CloudQube hosts for you, a shop you run elsewhere, or an API on your own server. Add monitoring to a project from the catalog. Point it at the URL you want to watch and set how often to check it. When a check fails, you’re alerted so you can look into it. Alongside up/down status, monitoring tracks response time , so you can also spot a service that’s still up but getting slow. Note Monitoring watches a service from the outside. To debug why something is down, start with Domain not resolving or check the service’s own dashboard. Last updated: Jul 22, 2026 Previous Share a public dashboard Next Connect Mollie --- ## Connect Mollie Source: https://docs.cloudqube.eu/guides/payments/connect-mollie/ Bring your shop Connect Mollie If you sell online with Mollie, you can connect your Mollie account to CloudQube to see your sales alongside the rest of your services. Add payments to a project from the catalog. Sign in to Mollie when prompted to authorise the connection (a standard, secure OAuth sign-in; you never share your Mollie password with us). Your sales data appears on the project’s dashboard. Reporting, not checkout CloudQube reads your Mollie payment data for reporting only. It isn’t part of your checkout, doesn’t move money, and never sees your customers’ card details. Your shop keeps taking payments through Mollie exactly as before. Last updated: Jul 3, 2026 Previous Uptime monitoring Next How billing works --- ## Deploy a static website Source: https://docs.cloudqube.eu/guides/static-sites/deploy/ Host a static website or single-page app on CloudQube Deploy a static website A static website is plain HTML/CSS/JS, or the build output of a framework like Astro, SvelteKit, Vue, or React. CloudQube serves it from an EU-only CDN with a free SSL certificate. Add a static website to a project from the catalog or a template. Deploy your built files (the contents of your dist / build folder). Each deploy is kept in your history, so you can roll back to a previous one. Your site goes live with HTTPS on its address on your project’s domain. Tip Deploy the output of your build, not your source. Run your framework’s build command locally (or in CI) and upload what it produces. Deploy automatically from your CI Section titled “Deploy automatically from your CI” Once the static website exists, you can deploy it on every push. Your own CI builds the site and uploads the result; CloudQube never clones or builds your repository. Any CI works, GitHub Actions and GitLab CI as well as EU-hosted runners like Forgejo/Codeberg or Woodpecker. Create the static website using the steps above, if you haven’t already. A deploy token belongs to one specific site. Generate a deploy token. Open the site in the dashboard, find the CLI / CI deploy section, and choose Generate deploy token . The token is shown once, so copy it now. Store the token in your CI as a secret named CQ_DEPLOY_TOKEN . Never commit it to your repository. Add a deploy job. Pick your CI below. Each one builds the site, zips the output folder ( dist by default), and uploads it. Adjust the build command and output folder to match your project. Shell / any CI Forgejo / Codeberg Woodpecker GitHub Actions GitLab CI Terminal window # Set CQ_DEPLOY_TOKEN in your environment / CI secrets first. npm ci && npm run build cd dist && zip -r ../site.zip . && cd .. curl -X POST https://app.cloudqube.eu/api/v1/projects/PROJECT_ID/cloudqube/SITE_ID/deploy-cli \ -H " Authorization: Bearer $CQ_DEPLOY_TOKEN " \ -F file=@site.zip .forgejo/workflows/deploy.yml name : Deploy to CloudQube on : push : branches : [ main ] jobs : deploy : runs-on : docker steps : - uses : actions/checkout@v4 - uses : actions/setup-node@v4 with : node-version : 20 - run : npm ci && npm run build - run : cd dist && zip -r ../site.zip . && cd .. - run : | curl -X POST https://app.cloudqube.eu/api/v1/projects/PROJECT_ID/cloudqube/SITE_ID/deploy-cli \ -H "Authorization: Bearer ${{ secrets.CQ_DEPLOY_TOKEN }}" \ -F file=@site.zip .woodpecker.yml steps : deploy : image : node:20 secrets : [ cq_deploy_token ] when : branch : main commands : - npm ci && npm run build - cd dist && zip -r ../site.zip . && cd .. - curl -X POST https://app.cloudqube.eu/api/v1/projects/PROJECT_ID/cloudqube/SITE_ID/deploy-cli -H "Authorization : Bearer $CQ_DEPLOY_TOKEN" -F file=@site.zip .github/workflows/deploy.yml name : Deploy to CloudQube on : push : branches : [ main ] jobs : deploy : runs-on : ubuntu-latest steps : - uses : actions/checkout@v4 - uses : actions/setup-node@v4 with : node-version : 20 - run : npm ci && npm run build - run : cd dist && zip -r ../site.zip . && cd .. - run : | curl -X POST https://app.cloudqube.eu/api/v1/projects/PROJECT_ID/cloudqube/SITE_ID/deploy-cli \ -H "Authorization: Bearer ${{ secrets.CQ_DEPLOY_TOKEN }}" \ -F file=@site.zip .gitlab-ci.yml deploy : image : node:20 rules : - if : $CI_COMMIT_BRANCH == "main" script : - npm ci && npm run build - cd dist && zip -r ../site.zip . && cd .. - curl -X POST https://app.cloudqube.eu/api/v1/projects/PROJECT_ID/cloudqube/SITE_ID/deploy-cli -H "Authorization : Bearer $CQ_DEPLOY_TOKEN" -F file=@site.zip Push. Your CI builds and uploads the site. Each upload appears in the site’s Deploy history , so you can roll back to a previous one at any time. Tip The dashboard shows the exact command for your site, with the real endpoint and project/site IDs filled in, under Deploy from your CI . Copy it from there rather than hand-editing PROJECT_ID / SITE_ID . Note The build runs on your own runner. The upload is a plain token-authenticated POST , so nothing ties you to a specific provider. The token is scoped to this one site; rotate or revoke it any time from the CLI / CI deploy section. Per-deploy limits match the dashboard upload. Last updated: Jul 21, 2026 Previous Handle bounces Next Add tracking to your site --- ## Domain not resolving Source: https://docs.cloudqube.eu/guides/troubleshooting/domain-not-resolving/ What to check when a domain doesn Domain not resolving Coming soon. Last updated: Jul 3, 2026 Previous Leaving CloudQube Next Email going to spam --- ## Email going to spam Source: https://docs.cloudqube.eu/guides/troubleshooting/email-going-to-spam/ Diagnose deliverability issues with SPF, DKIM, DMARC. Email going to spam Coming soon. Last updated: Jul 3, 2026 Previous Domain not resolving Next HTTPS certificate pending --- ## HTTPS certificate pending Source: https://docs.cloudqube.eu/guides/troubleshooting/https-certificate-pending/ Why a new site can briefly show a certificate warning, and when it clears. HTTPS certificate pending When a domain is newly pointed at a service, its HTTPS certificate is issued automatically, but only once the domain’s DNS has propagated far enough for the certificate authority to verify it. In the short window before that finishes, a browser may show a “not secure” or certificate warning. This is normal and usually clears within a few minutes. If it hasn’t cleared Section titled “If it hasn’t cleared” Give it up to an hour on a fresh domain. If the warning is still there after that, the usual cause is DNS: the domain isn’t pointing at CloudQube yet, so the certificate can’t be validated. Note Check the domain’s DNS first, following Domain not resolving . Once DNS resolves to CloudQube, the certificate is issued on the next attempt and the warning disappears. Last updated: Jul 3, 2026 Previous Email going to spam --- ## Plans and one-off purchases Source: https://docs.cloudqube.eu/concepts/pay-per-use/ One flat monthly plan for running services; one-off purchases like domains are paid at checkout. Plans and one-off purchases CloudQube charges you in two simple ways. The monthly plan Section titled “The monthly plan” Running services are covered by one flat monthly subscription: a base plan plus any add-ons you pick (like a bigger email tier). The plan renews on the same day each month, the day you subscribed, and every renewal produces a proper VAT invoice. Two days before each charge you get a heads-up email with the exact amount. The free tier needs no payment method: it covers sandbox use on a subdomain, and the fair-use allowances below. Anything on your own domain requires the base plan. Included fair use Section titled “Included fair use” Every project includes generous allowances: uptime checks, analytics pageviews, outbound emails, and site bandwidth. When you reach a cap the service pauses until the month renews or you pick a bigger add-on; there is never an overage bill. One-off purchases Section titled “One-off purchases” Things with a clear, finite cost, registering or renewing a domain, are paid at checkout the moment you buy them, at the exact price shown. Domains renew yearly; you get reminders well before, and auto-renew charges your saved payment method two weeks ahead so there is time to react if a payment fails. Cancelling Section titled “Cancelling” Cancel your plan any time: it stays active until the end of the month you paid for and simply does not renew. Anything that needs a paid plan (like a site on your own domain) pauses after a grace period; your data is kept and resubscribing picks up where you left off. Last updated: Jul 29, 2026 Previous What a qube is Next Your data & privacy --- ## Projects and templates Source: https://docs.cloudqube.eu/concepts/projects-and-templates/ How a project bundles qubes, and how templates fast-track setup. Projects and templates Coming soon. Last updated: Jul 3, 2026 Previous Your first project Next What a qube is --- ## What a qube is Source: https://docs.cloudqube.eu/concepts/qubes/ A qube is a single resource your project needs: a domain, an email sender, a website, analytics. Projects bundle qubes together. What a qube is A qube is one resource your project needs. Examples of qubes: A domain qube registers and renews a domain on your behalf. A DNS qube holds your DNS records. An email qube lets you send and receive email on your domain. A static website qube hosts and serves your site’s pages. An analytics qube counts visitors to your site without tracking them. A monitoring qube watches your site, or anything else with a URL, wherever it is hosted, and alerts you when something breaks. A custom connection qube brings numbers from a service you already run onto your dashboard, with the same charts and automation rules as everything else. A project is a collection of qubes that belong together. When you set up “my portfolio site”, that project might have a domain qube, a DNS qube, an email qube, a static website qube, and an analytics qube, all wired up so they reference each other automatically. Why we use the word “qube” Section titled “Why we use the word “qube”” Most platforms talk about “services”, “resources”, or “addons”. Those words have ten different meanings depending on who you ask. We picked something neutral so we could give it one clear meaning here. A qube is one thing your project depends on. Qubes vs widgets Section titled “Qubes vs widgets” Two related ideas you will see in the dashboard: Qubes are resources you actually use. They cost money. They show up in your invoices. Widgets are read-only views of your data: the analytics chart, the most recent emails, the list of failing checks. They live in the right sidebar and are toggled, not provisioned. If something costs money, it is a qube. If it just shows you data, it is a widget. Last updated: Jul 22, 2026 Previous Projects and templates Next Plans and one-off purchases --- ## Your data & privacy Source: https://docs.cloudqube.eu/concepts/your-data-and-privacy/ Where your data lives, who processes it, and how to read the details. Your data & privacy CloudQube is built to keep your data in the EU and under your control. EU-hosted. The services we run for you, and the data we host, live on EU infrastructure, and we don’t use non-EU sub-processors. One deliberate exception is under your control: if you point a custom connection or an uptime monitor at an endpoint outside the EU, we call that endpoint at your instruction. We provision on your behalf. CloudQube holds the provider accounts and sets services up for you, so you don’t manage separate cloud consoles. Sensitive values (passwords, connection strings, tokens) are encrypted at rest. No lock-in. You can export your data and transfer your domains out at any time. See Leaving CloudQube . The full detail is in the legal pages The authoritative, up-to-date detail on what we collect, why, who processes it, and your rights lives in our Privacy Policy and Terms of Service . This page is a summary and deliberately doesn’t duplicate them. Last updated: Jul 22, 2026 Previous Plans and one-off purchases Next Register a domain ---