Voroa Documentation
Voroa documentation
Learn how to deploy and run apps on Voroa. Connect a GitHub repository, ship on every push, add a managed database and a custom domain, and go live in India. New here? Start with your first deploy below.
Start here
- What is Voroa? A deploy platform (PaaS) built for India Voroa is a platform as a service that deploys apps from GitHub, runs them in India, and bills in rupees with a GST invoice. See how it works and who it is for.
- Deploy from GitHub: take a web app live, step by step Deploy a web app from your GitHub repository: connect GitHub, pick a branch, set build and start commands, and go live on HTTPS in India with auto-deploy.
- Auto-deploy from GitHub: ship on every git push Turn on auto-deploy so Voroa builds and ships your app on every push to your branch, and learn how to switch it on or off for each service from its settings.
- How to add a managed Redis or Postgres on Voroa Create a managed Redis or Postgres database on Voroa, get its connection URL once, and connect your service. Hosted in India, with trusted sources you control.
Quickstarts by framework
- Deploy a Node.js app from GitHub in India Deploy a Node.js app from GitHub in minutes on Voroa — no server or cPanel setup. Node.js hosting in India, billed in INR with GST invoices and UPI. Start free.
- Deploy a Next.js app from GitHub in India Deploy a Next.js app from GitHub in minutes on Voroa — no server setup. Next.js hosting in India, billed in INR with GST invoices and UPI. Start free.
- Deploy a React Vite app from GitHub: step by step Deploy a React app built with Vite from GitHub. Voroa runs npm run build, serves the dist folder with working client-side routes, and puts it on free HTTPS.
- Django deployment: deploy a Django app from GitHub Deploy a Python Django app from GitHub with gunicorn, WhiteNoise and PostgreSQL. Set ALLOWED_HOSTS, run migrations safely, and go live on HTTPS in India.
- Deploy a static site from GitHub with free HTTPS Step-by-step: connect a GitHub repository, pick the folder to serve, and publish a static site on Voroa. Add your own domain and roll back a bad deploy.
- Deploy a Docker app from your Dockerfile in India Build your service from your own Dockerfile on Voroa: choose the Docker runtime, set the Dockerfile path, and make the image listen on the port Voroa provides.
Getting Started
- What is Voroa? A deploy platform (PaaS) built for India Voroa is a platform as a service that deploys apps from GitHub, runs them in India, and bills in rupees with a GST invoice. See how it works and who it is for.
- Hosting for startups in India: what to pick at each stage Hosting for startups in India: shared hosting, VPS, PaaS or AWS at each stage, and the early choices (data location, billing, GST) that are costly to undo.
- Deploy from GitHub: take a web app live, step by step Deploy a web app from your GitHub repository: connect GitHub, pick a branch, set build and start commands, and go live on HTTPS in India with auto-deploy.
- Free instances on Voroa: what you get without paying Voroa's free plan: up to 15 services of 512 MB, one free database, 750 running hours a month shared by services and databases, 5 GB bandwidth, 500 build minutes
- Use Voroa with Claude Code or Cursor: ship, read logs, fix Let Claude Code or Cursor close the loop on Voroa: the agent pushes, watches the deploy, reads the build log when it fails, then fixes and redeploys on its own.
- Connect Claude, Cursor or OpenCode to Voroa over MCP Connect Claude Code, Claude Desktop, Cursor or OpenCode to Voroa's hosted MCP server. One URL, a scoped token or a sign-in, and nothing to install or run.
Not yet available
- Platform features by plan: what each Voroa plan includesSoon A side-by-side view of what changes when you move from one plan to the next, so you know exactly what you are buying on Voroa before you spend anything.
- Voroa FAQ: the questions developers ask mostSoon Short answers to the questions people ask most about deploying from GitHub, paying in rupees, GST invoices, managed databases and custom domains on Voroa.
- Templates: start a new service from a ready-made projectSoon How one-click templates work on a hosting platform, why they remove the first hour of setup on a new project, and how to start a service on Voroa today.
Migrate from...
Not yet available
- Migrate from Heroku to VoroaSoon What moving an app off Heroku actually involves: your buildpack, config vars, add-on database and custom domains, and how each of those maps onto Voroa.
- Migrate from Railway to VoroaSoon The four things you have to move when you leave Railway: the build, your variables, your database and your domain, and how each of them works on Voroa.
Compute
- Instance types and prices: CPU and RAM for every service Voroa instance types from Free (0.1 CPU, 512 MB) to Pro Ultra (8 CPU, 8 GB), priced in rupees with a GST invoice, and how to pick the right size for a service.
- SSH access: open a terminal inside your running service Connect to your running service over SSH with a key you add once: what you can do in a session, what is lost on the next deploy, and fixing a refused login.
- Idle sleep: what happens to a free service with no traffic Idle sleep stops a free web service that has had no requests and starts it on the next one. What can sleep, what never does, and how to handle cold starts.
- How to create a new service on Voroa Start a new service on Voroa: pick a web service, static site, worker, cron job, or database, then configure and deploy. A guide to the service chooser.
- Deploy a static site from GitHub with free HTTPS Step-by-step: connect a GitHub repository, pick the folder to serve, and publish a static site on Voroa. Add your own domain and roll back a bad deploy.
- Managed WordPress on Voroa: plans with CPU, memory and disk Create a Managed WordPress site on Voroa: WordPress and its database in one place, page caching, nightly backups, and plans that include CPU, memory and disk.
- Deploy a background worker: queues and consumers Run a long-running background worker from GitHub on Voroa — queues, consumers and processors with no web port. Hosted in India, billed in INR with GST.
- Schedule a task (cron) on a Voroa service Run a command on a schedule inside a running Voroa service - backups, cleanups and periodic jobs - with a cron expression. Hosted in India, billed in INR.
- Host cron jobs and background workers: which one you need How to tell whether your code belongs in a Voroa background worker or a cron job, why a program that finishes ends up restarting forever, and how to move it.
- Voroa MySQL: a managed MySQL 8 database Create a managed MySQL 8.4 database on Voroa: plans from 1 GB of RAM, TLS-only external access, database users, phpMyAdmin imports and WordPress setup.
- Voroa Key Value: a managed in-memory store Create a managed key-value instance on Voroa: plans from 256 MB to 10 GB, internal and TLS external connections, nightly snapshots, password rotation.
- Service disk: how much a service can write, and adding more See how much disk a web service or background worker is using, what every service includes, how to add disk in 5 GB steps, and why its files are temporary.
- Persistent disks: storage that survives a deploy Add a persistent disk to a web service or worker on Voroa: pick a mount path and size, what survives a deploy, the one-copy rule, growth, backups and restore.
Not yet available
- Web services: a public HTTP service on VoroaSoon What a web service is, how it differs from a background worker or a static site, and how a public HTTP service gets its address and certificate on Voroa.
- Private services: an internal service with no public addressSoon What a private service is, why an internal API or queue consumer should not be reachable from the public internet, and what Voroa offers for this today.
- Workflows: running multi-step jobs as a managed serviceSoon What a durable workflow is, why long multi-step jobs need retries and saved state, and how this differs from a background worker or from a scheduled task.
- Multi-service architectures: running an app as several servicesSoon How to split an application into a web service, a background worker and a database, why teams do it, and how each piece is created on Voroa right now.
Deploys
- Auto-deploy from GitHub: ship on every git push Turn on auto-deploy so Voroa builds and ships your app on every push to your branch, and learn how to switch it on or off for each service from its settings.
- Build pipeline: build minutes, build machines and limits How Voroa counts build minutes, which machine your builds run on, what Performance builds cost, and how a monthly limit caps what you can be billed each month.
- How to set build and start commands on Voroa Set the build and start commands Voroa uses for your app, change them any time from Settings, and redeploy with one click so the new commands take effect.
- Deploy hooks: trigger a deploy from a URL with Voroa Create a private deploy hook URL for your Voroa service, then trigger a new deploy from your CI, a CMS publish button or any script with one POST request.
- How to change your deploy branch or root directory on Voroa Change which Git branch Voroa deploys, or point a service at a subfolder of a monorepo, from Settings. Fix a wrong branch or path and redeploy in one click.
- Change the Git repository a service deploys from Point an existing Voroa service at a different connected repository from Settings, keep its domain and variables, and see what carries over and what not.
- Deploy from any Git URL, public or private Point an existing Voroa service at any https Git repository, public or private with an access token, and keep its URL, variables, databases and deploy history.
- Monorepo support: deploy many services from one repo Run several Voroa services from one repository. Give each its own root directory, and use build filters so a push rebuilds only the services it changed.
- Databases from your repo: Postgres and Key Value auto-linked Voroa reads your repo when you create a web service, suggests Postgres or Key Value, creates them with it, and adds DATABASE_URL or REDIS_URL for you.
- Deploy status: Live, Starting, Failed, and Build failed What the Voroa deploy statuses mean - Live, Starting, Failed and Build failed - what each one tells you about your service, and how to fix a deploy that failed.
- Deploy history and build log retention See your recent deploys, open any single deploy for its full build log, status, and timing, and learn how long build logs stay visible on each Voroa plan.
- Paid service not live yet? The first-build page explained Paid for a Voroa service but it is not live yet? Learn why a waiting page appears, how to fix a failed first deploy, and when your billing period starts.
- Service stopped by Voroa: why it happens and how to restart What the Stopped by Voroa badge means, why we stop a service that restarts without end, what happens to your code and data, and how to fix it and bring it back.
- Pull request preview environments: a live URL for every PR Give every GitHub pull request its own running copy of your app with its own URL. Turn previews on, test changes in a browser, and Voroa removes them on merge.
- Deploy a Docker app from your Dockerfile in India Build your service from your own Dockerfile on Voroa: choose the Docker runtime, set the Dockerfile path, and make the image listen on the port Voroa provides.
- Secrets and Docker builds on Voroa Why a credential must never be passed as a Docker build argument, where Voroa keeps secret values instead, and how your service reads them while it runs.
- How to add environment variables on Voroa Add and update environment variables for your Voroa service, and read them in your app. Values are stored encrypted and are never shown back once saved.
- Environment groups: share env variables across services Create an environment group on Voroa, link it to several services, and change a shared value once. Covers precedence, redeploy behaviour and current limits.
- Connect GitHub to Voroa and deploy on every push Connect your GitHub account to Voroa, choose which repositories it can read, deploy from them, ship on every push, and disconnect again whenever you want.
Not yet available
- How a deploy works on Voroa, from git push to liveSoon What happens between a git push and a live URL: the clone, the install, the build, the start and the switch over, and what a failure at each step means.
- Supported languages and runtimes on VoroaSoon How a build system works out which language your repository is written in, what it needs to find to do that, and which stacks Voroa builds and runs today.
- Troubleshooting a failed deploy on VoroaSoon The usual reasons a deploy fails, from a missing dependency to a wrong start command to a port your app never listens on, and how to read the log for each.
- Single-service previews: preview one service, not the whole stackSoon How previewing a single service works, when you want the web service previewed but not its database, and what preview environments Voroa offers today.
- Deploy a pre-built image from a container registrySoon How deploying an image you have already built differs from building from source, why teams do it, and what a private registry needs for the pull to work.
- Native runtimes: how Voroa builds without a DockerfileSoon How a build system detects your language from the repository, installs the right runtime, and produces a running service with no container file from you.
- Default environment variables Voroa sets for your serviceSoon The variables a hosting platform injects into every service, the port above all, and why your code must read them instead of hardcoding a fixed value.
- Connect GitLab to Voroa and deploy on every pushSoon Connect your GitLab account to Voroa, deploy a GitLab project, ship automatically on every push, and understand exactly what access Voroa asks for and why.
- Connect Bitbucket to VoroaSoon What connecting a Bitbucket repository to a hosting platform involves, the access it needs to clone and build your project, and what Voroa supports today.
Quickstarts
- Deploy a Node.js app from GitHub in India Deploy a Node.js app from GitHub in minutes on Voroa — no server or cPanel setup. Node.js hosting in India, billed in INR with GST invoices and UPI. Start free.
- Deploy a React Vite app from GitHub: step by step Deploy a React app built with Vite from GitHub. Voroa runs npm run build, serves the dist folder with working client-side routes, and puts it on free HTTPS.
- Deploy a Next.js app from GitHub in India Deploy a Next.js app from GitHub in minutes on Voroa — no server setup. Next.js hosting in India, billed in INR with GST invoices and UPI. Start free.
- Django deployment: deploy a Django app from GitHub Deploy a Python Django app from GitHub with gunicorn, WhiteNoise and PostgreSQL. Set ALLOWED_HOSTS, run migrations safely, and go live on HTTPS in India.
Workflows
Not yet available
- Introduction to workflows: durable multi-step jobsSoon What a workflow engine does that a plain background job cannot, why saved state between steps matters, and where this fits alongside workers and cron.
- Workflows tutorial: build your first durable jobSoon A walkthrough of writing a multi-step job whose steps can each be retried safely, and what such a tutorial covers on a platform that runs workflows today.
- Workflow limits and pricingSoon The limits a workflow engine normally applies, from step duration to retry counts and concurrent runs, and how that kind of service is usually priced.
- Defining workflow tasks and stepsSoon How a multi-step job is described in code, what makes a step safe to retry, and why the boundary you draw between steps decides how well retries work.
- Triggering and monitoring workflow runsSoon The ways a durable job is normally started, from an API call to a schedule to an event elsewhere, and what you need to see while a run is in progress.
- Developing workflows on your own machineSoon Why a durable job engine needs a local mode, what running one on your own machine lets you test, and how to test multi-step logic without one on Voroa.
- Workflows TypeScript SDK referenceSoon What a workflow SDK gives a TypeScript project, how the steps and retries get expressed in code, and what Voroa offers today for durable background jobs.
- Workflows Python SDK referenceSoon What a workflow SDK gives a Python project, how steps and retries are expressed in code, and what Voroa offers for long multi-step jobs at the moment.
Voroa Postgres
- How to add a managed Redis or Postgres on Voroa Create a managed Redis or Postgres database on Voroa, get its connection URL once, and connect your service. Hosted in India, with trusted sources you control.
- PostgreSQL connection details and how a service uses them What each PostgreSQL connection detail means on Voroa, which of them you can look up again later, and how a service reads them as an environment variable.
- Connect to your Voroa PostgreSQL database from anywhere Managed PostgreSQL on Voroa gets a public TLS endpoint the moment it is created. Connect with pgAdmin, DBeaver or psql, and restrict who may reach it.
- Create extra PostgreSQL users for each app or tool on Voroa Give a reporting tool or teammate its own PostgreSQL login on your Voroa database instead of your main one, and rotate a password with no downtime for your app.
- Enable PostgreSQL extensions: pgvector, pg_trgm and more Enable PostgreSQL extensions on a Voroa managed database without a restart: uuid-ossp, citext, pg_trgm, pgcrypto, hstore and pgvector for vector search.
- How to migrate a PostgreSQL database to Voroa: import guide Migrate an existing PostgreSQL or Redis database to Voroa by pasting its connection string. No pg_dump files; Voroa checks, copies and never stores it.
- Upgrade a database that runs on its own server Move a database that runs on its own server to a bigger plan: what you pay, how long it is down, how storage grows, and why a plan cannot be made smaller.
- Managed database storage limits Every managed Voroa database has a storage limit. See how much you are using, raise the limit when you need more, and restore writes if it goes read-only.
- Database pause: what happens to an unused free database A free Voroa database with no queries for 7 days is paused. How idle is measured, what happens to your data and backup, and how to resume it in one click.
- Availability and recovery for managed PostgreSQL on Voroa What happens if your Voroa managed PostgreSQL database or its server fails: honest recovery times, backup schedules, data-loss windows, and how restores work.
- Connection pooling for PostgreSQL Why PostgreSQL runs out of connections before it runs out of capacity, what the pooled endpoint on your Voroa database changes, and which endpoint to use when.
Not yet available
- PostgreSQL credentials: users, passwords and connection stringsSoon What each part of a database connection string means, why an application should not use the superuser, and how Voroa presents your database credentials.
- Upgrading your PostgreSQL major versionSoon Why a PostgreSQL major version upgrade is not simply a restart, what really has to happen to your data, and how to move to a newer version on Voroa now.
- Logical replication: stream changes out of PostgreSQLSoon What logical replication does, why teams use it to migrate a database with almost no downtime or to feed an analytics system, and where Voroa stands now.
- Flexible database plans: sizing storage and compute apartSoon Why a database's memory and its disk grow at different rates, how each one fails when it runs short, and how storage is sized on a Voroa PostgreSQL database.
- High availability for PostgreSQL: standby and failoverSoon What high availability means for a database, how a standby copy and automatic failover shorten an outage, and what Voroa provides for recovery right now.
- Read replicas: serve reads from a second copy of your databaseSoon What a read replica is, why moving heavy read queries off the primary protects your writes, and what a replica can never be trusted to do for you today.
- Database admin apps: connecting a GUI to PostgreSQLSoon What a database GUI gives you over a command line, what it needs in order to reach a managed database, and how to connect one to Voroa Postgres today.
- Repacking tables: reclaiming space in PostgreSQLSoon Why a PostgreSQL table keeps on growing even after you delete rows, what repacking does about that, and what you can do about bloat on Voroa right now.
- Troubleshooting slow PostgreSQL queriesSoon The usual reasons a database becomes slow, from a missing index to too many connections to table bloat, and how to work out which one is affecting you.
Object Storage
Networking
- Inbound IP rules: allow only IP ranges you trust Allow only the IP ranges you trust to reach a Voroa web service: who can set rules, setup, CIDR rule format, what a blocked request sees, and common questions.
- Edge caching: serve static content from the edge Serve a paid Voroa web service's static content from a global edge cache: setup, cacheable file types, cache eligibility, purging, Cache-Control rules.
- WebSockets on Voroa: send and receive data in real time Run WebSockets on Voroa web services: framework setup, connecting over wss, keepalive pings, reconnecting after deploys, saving session state, and limits.
- Automatic HTTPS and SSL on Voroa Every Voroa service gets free, automatic HTTPS. SSL/TLS certificates are issued and renewed for you, on your default address and on every custom domain you add.
- How to add a custom domain with free HTTPS: step by step Point your own domain, like myapp.in or www.myapp.in, at your Voroa service with one DNS record. Voroa verifies it and issues a free HTTPS certificate.
- How to add a wildcard domain like *.myapp.in on Voroa Send every name under your domain, like shop.myapp.in and blog.myapp.in, to one Voroa service with a wildcard domain, two DNS records and automatic HTTPS.
- Change your service's onvoroa.com subdomain Rename your service's free onvoroa.com address, like my-api.onvoroa.com, from Settings. What happens to the old name, the 30-day hold, and what to update.
- New Voroa services get an onvoroa.com address: what changes New Voroa services get a name.onvoroa.com address. Existing getvoroa.com addresses keep working as before and also answer on onvoroa.com. Nothing to do.
- Private networking between your services: step by step Let your Voroa services call each other on any port by an internal address, without going over the public internet. Find the address, connect, and test it.
- Outbound IP addresses: what Voroa connects out from The addresses Voroa connects out from, which to allow through your database or partner firewall, why you should allow all of them, and when the list changes.
- Outbound bandwidth: what counts and what it costs What outbound bandwidth Voroa counts for every service in a workspace, how much each plan includes, how extra use is billed, and where to see usage by service.
Not yet available
- Regions: where your Voroa service actually runsSoon What a region is, why the distance between your users and your server shows up in every request, and where services and databases run on Voroa right now.
- Point a Cloudflare domain at your Voroa serviceSoon What DNS records a custom domain needs, what Cloudflare's proxy setting changes about certificate issue, and how to add your own domain to Voroa today.
- Point a Namecheap domain at your Voroa serviceSoon Where DNS records live in a Namecheap account, the difference between its basic and advanced DNS screens, and how to add a custom domain on Voroa today.
- Point any DNS provider at your Voroa serviceSoon The DNS records a custom domain needs whichever provider you use, why an apex domain behaves differently from a subdomain, and how to set each one up.
- Private links to services outside the platformSoon What a private link is, why teams use one to reach a database or an internal system without crossing the public internet, and where Voroa stands today.
- Dedicated IP addresses for outbound trafficSoon When a partner insists on a fixed source address, what a dedicated outbound IP gives you over a shared one, and what Voroa offers for that need today.
- Handling network changes and dropped outbound connectionsSoon Why a long-lived outbound connection eventually breaks, why your code must expect it, and how to make a service survive a reset without failing a request.
- Custom response headers for a static siteSoon What response headers control on a static site, from browser caching through to security policy, and how your static site is served on Voroa at present.
- Redirects and rewrites for a static siteSoon The difference between a redirect and a rewrite, why a single-page app needs one to survive a refresh, and what Voroa handles for your static sites now.
Operational Controls
- Understanding your Voroa dashboard and services Read your Voroa dashboard: a card grid of web services and managed databases with status, live URL, plan, region, last updated, and Active or Suspended filters.
- SSH and shell access to a running service What a shell inside a running service is for, why anything you change by hand is lost on the next deploy, and where the guide for connecting to one lives.
- Projects and environments: grouping related services Group the services that make up one application into a project, split them across environments like Production and Staging, then rename or remove one safely.
- Service resource usage: see your RAM and CPU on Voroa See how much memory and CPU each Voroa service uses against its plan limit on the service Overview, and get an early warning before it runs out of headroom.
- Scaling a service: bigger instances or more of them The difference between scaling up and scaling out, which one your bottleneck actually calls for, and how to change the size of a Voroa service right now.
- Rollbacks: putting the previous version back How to return a Voroa service to an earlier working version without a rebuild, what a rollback restores, and the one thing it deliberately does not restore.
- Maintenance mode: a holding page instead of a broken site Turn on maintenance mode for a Voroa service so visitors see a holding page during planned work, use a page of your own, and know what keeps running meanwhile.
Not yet available
- One-off jobs: run a command once against your serviceSoon What a one-off job is for, from a database migration to a data backfill, and how to run a task against your Voroa service and its database at the moment.
- Infrastructure as code: define your services in a fileSoon What it means to declare your services in a file kept in your own repository, what that buys a team over time, and how Voroa services are created today.
- The voroa.yaml blueprint referenceSoon What a blueprint file declares, from each service and its size to variables and databases, and how services on Voroa are configured through the dashboard.
- Managing Voroa with TerraformSoon What a Terraform provider does for a hosting platform, why teams manage their services this way, and how Voroa services are created and changed today.
Observability
- Health checks: proving a service is actually working What a health check endpoint is, why a running process is not the same thing as a working one, and how to set the exact path Voroa probes after every deploy.
- Deploy notifications by email and Slack Voroa emails you when a build fails, a new version will not start, or a service keeps restarting. What each email says, who gets it, and how to turn alerts off.
Not yet available
- Uptime best practices for a service you run yourselfSoon The habits that keep a small service reliable, from graceful shutdown to timeouts to knowing before your users do, and where Voroa helps you right now.
- Webhooks: get told when a deploy finishes or failsSoon What an outgoing webhook is, why teams feed deploy events into their own chat and on-call systems, and how to see the state of a Voroa deploy right now.
- Service metrics: memory, processor and request volumeSoon Which numbers actually tell you whether a service is healthy, how to read a memory graph before a crash, and where to see your usage on Voroa right now.
- Streaming metrics out with OpenTelemetrySoon What OpenTelemetry standardises, why teams stream their metrics into a single monitoring tool of their own choosing, and what Voroa exposes about services.
- Logs on Voroa: build logs and what your service printsSoon The difference between a build log and a runtime log, why each matters at a different moment, and how long logs are kept for a service running on Voroa.
- Log streams: shipping logs to your own systemSoon Why teams forward logs to a system they control themselves, what syslog and HTTPS delivery each suit, and how long Voroa keeps the logs it holds today.
Integrations
- Voroa MCP server: manage your hosting from an AI client Voroa's MCP server lets an AI client read logs, deploy and manage your services. What MCP is, which tools exist, and where the boundary of what it can do sits.
- Voroa CLI: deploy and manage services from your terminal Install the Voroa CLI with npm, sign in, and deploy, tail logs, set variables, manage databases, cron jobs and storage from your terminal or a CI pipeline.
- Voroa CLI command reference Every Voroa CLI command: services, deploys, logs, environment variables, databases, domains, SSH, API tokens and workspaces, with their flags and exit codes.
- Let your AI agent run the Voroa CLI: deploy, check and fix Give Claude Code, Cursor or any coding agent the Voroa CLI. One guide command teaches it the rules: JSON output, coded errors, exit codes and safe limits.
Not yet available
- A REST API for VoroaSoon What a public API lets you automate on a hosting platform, why teams script service creation and deploys with one, and how Voroa services are managed today.
- Voroa REST API referenceSoon What an API reference documents, from authentication and endpoints through to rate limits and error shapes, and how you manage services on Voroa today.
- OIDC: short-lived credentials instead of stored keysSoon How OpenID Connect lets one system prove its identity to another without a stored secret, why that removes a real risk, and where Voroa stands on it today.
- Send Voroa service data to DatadogSoon What Datadog does with the metrics and logs from a hosted service, why teams centralise them in one place, and what your application can send from Voroa.
User Management
- Invite team members and manage roles in your workspace Invite teammates to your Voroa workspace by email and give each one a role: Admin, Developer, Contributor, Viewer or Billing. See what every role can do.
- Workspaces on Voroa: switch between and create workspaces Organise your work on Voroa with workspaces: switch between them and create a new one. Each workspace has its own services, databases, members and billing plan.
- How to name and rename your workspace on Voroa Give your Voroa workspace a name and change it any time from Settings. Your workspace name appears in the sidebar and breadcrumbs across the dashboard.
- Workspace settings on Voroa: name, email, and plan Manage your Voroa workspace settings — rename your workspace, set a notification email, find your workspace ID, and see your plan. A guide to the settings page.
- Account settings on Voroa: your name, email, and password Manage your personal Voroa account — set your full name, see the email you sign in with, and change or set your password. A guide to the account settings page.
- Two-step verification: authenticator apps, passkeys, codes Turn on two-step verification for your Voroa account with an authenticator app or a passkey, save recovery codes, and learn what to do if you lose a device.
- Require two-factor or Google sign-in for a workspace Require every member of your Voroa workspace to use two-factor authentication or sign in with Google, and see what a member who does not comply can still do.
- How to sign in to Voroa with GitHub Sign in or sign up for Voroa using your GitHub account in one click. Learn how Continue with GitHub works and how it links to an existing email account.
- Sign in to Voroa with Google Sign in to Voroa with your Google account, create a new account in one click, or connect Google to an account you already have from your account settings.
- How to sign in to Voroa with an email code Sign in or sign up for Voroa with a one-time code sent to your email — no password to remember. Learn how email sign-in codes work and how to resend one.
- Audit logs: see who changed what in your Voroa workspace Voroa audit logs record the changes made in your workspace - who made each one, when, and from the dashboard, an API token or an AI agent. Export as CSV.
Not yet available
- Workspace plans: what a paid workspace changesSoon How a workspace-level plan differs from the size of one service, what each of the two actually controls, and how plans work on a Voroa workspace today.
- Organizations: one account across many workspacesSoon What an organization layer adds above workspaces, why larger teams want central control of members and billing, and how Voroa is structured right now.
- SAML single sign-on for a teamSoon What SAML single sign-on gives a company, why joining and leaving are the real problems it solves, and how people sign in to their Voroa account today.
Billing
- Usage and billing on Voroa: build minutes and bandwidth See your Voroa usage for this period - build minutes and bandwidth against your plan's included amounts - and how what is measured turns into your bill.
- Add a payment method and read your billing summary on Voroa Set up automatic monthly payment on Voroa by UPI AutoPay or card, with a small verification charge that is returned, and read your billing summary line by line.
- See your payment summary before you pay on Voroa See a payment summary before confirming a paid Voroa plan: the prorated amount due now, 18% GST shown separately, and your recurring monthly charge and date.
- Voroa billing emails: every notice we send about your money Every email Voroa sends about your money: the notice before a renewal, a failed payment, a move to free limits, a recovered payment and auto-pay ending.
- Pay a renewal by payment link when auto-debit fails What a Voroa renewal payment link is, why you got one instead of an automatic debit, how long the link stays valid, and what happens if it goes unpaid.
- Unpaid renewal: free limits, stopped databases, getting back What Voroa does when a monthly renewal goes unpaid: how many attempts, how long you have, what changes for apps and databases, and when data is lost for good.
- What cloud hosting actually costs an Indian business How to budget cloud hosting in India properly: the line items beyond the instance price, which of them are actually charged, and where teams underestimate cost.
- GST invoice for cloud hosting in India, explained Cloud hosting in India carries 18% GST. A valid GST invoice with the supplier's GSTIN lets a registered business claim it back as input tax credit.
- Do you need a GST number to buy cloud hosting in India? Whether you need a GSTIN to pay for cloud hosting in India, what changes on your invoice once you add one, and why adding it before your first payment matters.
- Input tax credit on cloud hosting: how to actually claim it The four conditions a cloud hosting invoice must meet before GST input tax credit is allowed, when the credit appears in GSTR-2B, and why claims get disallowed.
- What a GST invoice for cloud hosting must contain The fields an Indian GST tax invoice for cloud hosting must carry, why a payment receipt is not a substitute for it, and how to check the invoice you were sent.
- Reverse charge on foreign cloud hosting, explained Why paying a cloud host outside India makes you liable for the GST yourself under reverse charge, what import of service means in practice, and what it costs.
- Cloud hosting billed in INR, paid by UPI Why paying for cloud hosting in Indian rupees over UPI beats dollar billing: no forex markup, no card declines, predictable costs and a GST invoice every time.
- Paying for cloud hosting from India Which payment methods work for cloud hosting from an Indian account, why foreign subscriptions fail on Indian cards, and how to pick a method that keeps going.
- UPI AutoPay for cloud hosting: mandates, limits, failures How a UPI AutoPay mandate works for a recurring cloud hosting bill, the per-debit ceiling that catches growing accounts, and the common reasons a mandate fails.
- INR vs USD cloud hosting: what a dollar bill really costs Is dollar-priced cloud hosting cheaper for an Indian business? Count the card forex markup, GST on that fee, exchange swings and reverse charge, worked out.
- Voroa Assistant: ask a question, get the right docs page Ask the Voroa Assistant a question in your dashboard and get the docs pages that answer it. It searches our docs only; your question never leaves Voroa.
- Contact support on Voroa: open a support case Get help on Voroa by opening a support case from your dashboard: set a priority, follow our replies and answer back from the support center until it is solved.
- Request a feature: vote on the Voroa feedback board Suggest features for Voroa and vote on ideas from other developers on the public feedback board. Sign in with your Voroa account and follow the roadmap there.
Platform Protections
- Voroa security overview: DDoS, HTTPS, 2FA and backups What Voroa does to protect your services and data: DDoS protection, HTTPS, inbound IP rules, encrypted secrets, account 2FA, team roles and daily backups.
- DDoS protection for a service's Voroa address What a denial of service attack does, how DDoS protection absorbs floods before they reach a service, what changes for uploads, slow requests and visitor IPs.
- Data residency in India: where your app and data run Where your app, database and backups are held, what the DPDP Act 2023 expects of you as a business, and which parts of data compliance stay your responsibility.
Not yet available
- Platform maintenance: planned work and what it means for youSoon Why a hosting platform needs maintenance windows at all, what a well-run one looks like from your side, and how to make your service survive a restart.
- Certifications and compliance standards, explainedSoon What certifications such as SOC 2 and ISO 27001 actually attest to, why an independent auditor rather than a vendor decides, and what Voroa holds today.
- HIPAA and health data hosting, explainedSoon What HIPAA requires of a service handling United States health data, what a business associate agreement is for, and what Voroa offers for this today.
- Best practices for handling sensitive personal dataSoon The engineering habits expected of any application handling sensitive personal data, from access logging to encryption to retention, explained plainly.
- Shared responsibility: what the platform secures and what you doSoon Where a hosting platform stops securing and your application begins, the gaps teams assume are covered when they are not, and how that applies on Voroa.
- Penetration testing policy, explainedSoon What a penetration test is, why a hosting provider must be told before you run one against your own application, and what Voroa's position is on this today.
Compare
Not yet available
- Voroa and Heroku compared for teams building in IndiaSoon An honest look at how Voroa and Heroku differ on deployment, hosting location, currency and invoicing, and which questions decide it for an Indian team.
- Voroa and Vercel compared for teams building in IndiaSoon How Voroa and Vercel differ in what they host, where they run it, and how they bill, and which of those differences actually matters to an Indian team.