Brikseka.

Business Tools · Online presence

Cloud and hosting

Hosting and cloud billing sit in the company’s name, on the company mailbox. A personal AWS, Vercel, or cPanel account is the same class of problem as a personal Gmail: the operating file does not match the legal entity.

For most founder websites, Cloudflare or Vercel is enough: HTTPS, the company domain, invoices to the company. When the product needs real infrastructure, we open AWS, Google Cloud, or Azure against the same domain and mailbox, with MFA and billing the company can explain. We do not leave production on a personal hobby account, and we do not open a hyperscaler account as theatre if a simple host will serve the site a bank is about to open. The cloud account is not a substitute for the website or the mailbox; it comes after both exist.

Book a confidential consultationAll business tools
In whose name
The company’s account, company email, and a payment method the company can hold
For a founder site
Cloudflare or Vercel is usually enough
For infrastructure
AWS, Google Cloud, or Azure — after the mailbox exists

How we work

From shortlist to a filed application

  1. 1

    Mailbox first

    Cloud sign-up uses the company email. We do not open AWS on a personal Gmail.

  2. 2

    Account

    We open the host or the cloud organisation in the company’s name and turn on MFA.

  3. 3

    Put the site on it

    The company domain points here. Invoices go to the company. The client holds the login.

Cloud accounts

The cloud bill has to sit in the company’s name. A founder’s personal AWS or Google Cloud account, with a personal card and a personal email, is the same class of problem as a personal Gmail: the operating story does not match the legal entity. We open the account after the company and the mailbox exist.

  • Amazon Web Services

    aws.amazon.com

    AWS is the default cloud for companies that need compute, object storage, or a serious production environment. The account is opened with the company email, the company legal name, and a payment method the company can hold. Root credentials are not left on a personal laptop with no recovery plan. Route 53, if we use it for DNS, lives in this same account so invoices tell one story.

    We brief this when the company will run infrastructure on AWS, or already does on a personal account that must be moved.

    How we help

    We open the organisation in the company’s name, attach the company mailbox and billing, set MFA, and hand over the account so the company owns it. Amazon decides. We do not run the production workload as a substitute for the client’s engineers unless that is a separate mandate.

  • Google Cloud

    cloud.google.com

    Google Cloud is the natural pair when the company already uses Google Workspace. Billing, IAM, and support sit next to the mailbox. A personal Gmail with a Google Cloud trial is not a company account. We open a Cloud Identity / organisation that matches the Workspace domain.

    We brief this when the company is already on Google Workspace, or when GCP is the cloud the product requires.

    How we help

    We attach Cloud to the company domain, set billing in the company’s name, and move any personal projects that should belong to the entity. Google decides.

  • Microsoft Azure

    azure.microsoft.com

    Azure is the cloud we brief when the company is on Microsoft 365, or when a client, a bank, or a public-sector counterpart in the company country expects Microsoft. The tenant, the mailbox, and the cloud bill should be one organisation. A personal Microsoft account with an Azure trial is not that organisation.

    We brief this when the operating stack is Microsoft, or when Azure is specified.

    How we help

    We create or take over the Azure tenant against the company domain, set billing, and align it with the Microsoft 365 admin. Microsoft decides.

Application hosting

Most founder websites do not need a full AWS estate. They need a host that bills the company, serves HTTPS, and stays up when a bank opens the link. These are the hosts we use for that.

  • Cloudflare

    www.cloudflare.com

    Cloudflare is DNS, CDN, and, for many of our founder sites, the host (Pages or Workers). Putting the domain, the DNS, and the site on one account in the company’s name is the cleanest operating file we can give a reviewer. It is also the usual place we put email authentication records.

    We brief this on most new websites we stand up, and whenever the domain already sits on Cloudflare.

    How we help

    We put the domain on Cloudflare, publish the site, and set DNS for mail. Cloudflare decides the account. The company holds the login.

  • Vercel

    vercel.com

    Vercel hosts Next.js and similar applications. We use it when the site is a proper web app rather than a page builder. The team, the project, and the billing have to be the company’s. A personal hobby account with a .vercel.app URL is not what we submit to Stripe.

    We brief this when the website is an application we (or the client’s engineers) deploy as code.

    How we help

    We create the team in the company’s name, attach the domain, and set billing. Vercel decides. Production stays on the company domain.

  • DigitalOcean

    www.digitalocean.com

    DigitalOcean is a straightforward cloud for a VPS, an app platform, or managed databases when AWS would be disproportionate. WordPress on a droplet, billed to the company, is a common file. The account still needs company email and company billing.

    We brief this when the company needs a simple server or a WordPress host, not a hyperscaler.

    How we help

    We open the account in the company’s name, provision the host, and put the site on the company domain. DigitalOcean decides.

Provider lists are indicative. We confirm current availability during consultation. Official websites open in a new tab; Brikseka is not those companies, and we do not guarantee their approval.

Frequently asked questions

Do I need AWS for a company brochure site?

No. Cloudflare or Vercel on the company domain is the usual founder-site host. We open AWS, Google Cloud, or Azure when there is infrastructure to run, or when an existing personal cloud account must be moved into the company.

Can we keep my personal Vercel or AWS account?

Not as the production account. We create a company team or organisation, move the project, and attach company billing. The personal account can stay for experiments; it should not be what a reviewer sees on the invoice.

Who pays the bill?

The company. That is the point. A personal card on a personal email is the file we are replacing.

Also in online presence

Related tools

Consultation

Start a confidential conversation

Tell us what you are building or where you need to move. We respond within one business day.

Confidential. We respond within one business day.