Everything the order form will ask you for, in the order it asks, with the exact steps to create each value in your own cloud account.
How ordering works
Pick a service on the order form. Each service page lists the exact fee and whether it runs on Google Cloud or Oracle Cloud.
Fill the form. It asks for your cloud project, keys and addresses, with the expected format inline. Every field links back to this page for the step-by-step.
Pay by UPI and put the transaction reference in the form. Nothing is created until that payment is matched, so you are never billed for a server you did not ask for.
We verify, then build. A human checks your reference against the bank statement, approves the order, and only then does anything get provisioned.
You get the keys. The service installs itself, answers health checks and hands over. Every credential we held is deleted on success.
Then what? Your service appears in Your services, where you can see its status, its addresses, and the next steps for that particular service. Order status is also readable any time from the order status box on the landing page — status and amount only, never your credentials.
Order field guides
Every value the order form asks you to go and create lives below, in the same order the form asks for it. Open each link from the form in a new tab, follow the steps, paste the result back.
Don't have a cloud account? Either cloud signs up in about five minutes.
Vishwakarma never hosts anything — every service lives on a cloud account you own, so you need the account before you order. Both clouds below offer a free tier that covers the smallest machine we sell. Signing up costs nothing and does not commit you to an order.
Google Cloud: go to console.cloud.google.com → sign in with a Google account → accept the terms and create a free-trial project. No card is required to explore; the order form adds the project, service account and SSH key step by step.
Oracle Cloud: go to signup.oraclecloud.com → create an account with an email and a card (Oracle holds it but does not charge the Always Free tier). Your home region is where the free VM is free, so pick the one nearest you (hyderabad or mumbai).
No account — no order. If you prefer not to create a cloud account, Vishwakarma cannot host a service for you: the machine, data and keys stay in your account by design, and we do not rent capacity of our own.
GCP project
Go to console.cloud.google.com and sign in with the Google account that will own the machine.
Create a project (one per service — deleting the project later removes everything, which is the point).
Copy the project ID (lowercase, e.g. asha-n8n-prod) — not the display name — into the form.
Enable billing on the project and turn on the Compute Engine API. The free tier still requires a card; nothing is charged for an e2-micro in a free-tier region.
GCP service account email + private key
In your project, open IAM & Admin → Service Accounts → Create service account.
Grant it the Compute Admin role — this is the only permission it needs, and only inside this project.
Open the account → Keys → Add key → Create new key → JSON. A file downloads.
From that file: client_email goes in the email field; the whole private_key block (both marker lines included) goes in the key field.
Scope. Use this account for this order only. It can only touch the project you made it in, and we delete our copy the moment the build succeeds.
Cloudflare tunnel hostname + token
In your Cloudflare dashboard, open Zero Trust → Networks → Tunnels → Create a tunnel (Connector type).
Add a public hostname: subdomain n8n on a domain whose DNS Cloudflare already manages, service http://localhost:5678.
Use that full hostname (e.g. n8n.yourdomain.com) in the form.
On the tunnel overview page Cloudflare shows a cloudflared install command containing a long token starting with eyJhZG1pbiI6 — copy only the token into the form.
Why a tunnel. The VM dials out to Cloudflare, so no port is ever opened on the machine. Your domain must already be on Cloudflare for this to work.
SSH public key
If you already have ~/.ssh/id_*.pub, print it and paste the whole single line — done.
Otherwise generate one with the command below, accepting all defaults (no passphrase needed for this use).
Paste the .pub file contents here — the public key only, never the private one.
ssh-keygen -t ed25519
Windows. This runs as-is in PowerShell (Windows 10+), Terminal, or any shell. View the key with cat ~/.ssh/id_ed25519.pub (or type the file in PowerShell).
GitHub username + backup repository
Your username is the plain handle in your profile URL (github.com/NAME).
Create a new private repository (empty — no README needed; the first backup fills it).
Paste its HTTPS URL (e.g. https://github.com/you/backup.git) in the form.
Keep it private. Hourly database snapshots land here. The account that owns it must match the username above, or the token below cannot write to it.
GitHub fine-grained token
GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
Under Repository access choose Only select repositories and pick the backup repo — nothing else.
Under Permissions → Repository → Contents set Read and write. Leave everything else at no access.
Copy the token immediately — GitHub never shows it again. Paste it in the form right away.
Least privilege. A classic token or an over-scoped fine-grained token works too, but then a leak reaches further. This shape is the minimum that functions.
Oracle Cloud API credentials (tenancy, user, fingerprint, key)
Sign in to the OCI console and click your profile icon (top right) → Tenancy. Copy the tenancy OCID — that is the first field.
Open Identity → Users and create a dedicated user for automation (not your root login). Open it and copy its OCID — that is the second field.
On that user page: API keys → Add API key → Generate key pair. Download the private key, and copy the fingerprint shown beside it — sixteen hex pairs like aa:bb:cc:….
Paste the whole downloaded private-key file, both marker lines included, in the key field.
Scope. Give the user membership in a group with permission to manage instances in one compartment only — never tenancy-wide admin. We hold the key in request memory and delete our copy at handover.
Compartment: Identity → Compartments — copy the OCID. Your tenancy root OCID works too, since it is itself a compartment. One compartment per service keeps deletion clean.
Region: use your tenancy's home region (the region selector in the console header shows it). The Always Free micro is only free there — anywhere else bills at standard rates.
Availability domain: the region menu lists ADs like Uocm:AP-HYDERABAD-1-AD-1. Copy the full name exactly, including the prefix.
Subnet: Networking → Virtual cloud networks → your VCN → Subnets — copy any subnet OCID with internet access. Its security lists stay entirely yours: the engine never writes them.
Which ports must be open? For n8n (tunnel-backed) the VM dials out, so no ingress rule is needed. For a bare VM or a Docker host the subnet's security list must already allow TCP 22 inbound (your SSH login — and your Docker CLI, since the Docker API is never exposed) and TCP 8080 inbound (the readiness check we probe at handover) — add those two rules before the order is approved.
Free-tier shapes. E2.1 Micro is fixed-size (1 OCPU, 1GB). The Ampere A1 Flex shape follows later with its own sizing step — for now the catalogue offers the free micro only.
n8n encryption key
Run the command below — it prints one random key. Same command on macOS, Linux and Windows.
Paste the output in the form, then save it in a password manager.
Without this exact key, nobody — not you, not us — can ever decrypt the credentials n8n stores. There is no recovery.
openssl rand -base64 32
Windows. Run it in Git Bash (ships with Git for Windows). Native PowerShell alternative: [Convert]::ToBase64String((1..32 | ForEach-Object { Get-Random -Maximum 256 })) — same 44-character shape, either output works.