FAQ

A scannable reference for everyday questions about Inhank Cloud. For deeper explanations, follow the links.

A developer platform for deploying and running applications straight from a Git repository. You push code, we build it, run it, route traffic, and give you logs + a dashboard. No infrastructure to manage.

See How it works.

Who is it for?

Developers shipping APIs, side projects, and small-to-medium production services. If you've used Railway, Render, or Fly.io, you'll feel at home.

No. New accounts receive a small one-time signup credit. You add credits to your wallet via Razorpay (UPI / cards / netbanking) only when you need more. See Billing.

Deployments & builds

How long should a build take?

First build of a service: 2–4 minutes
Subsequent builds: typically under a minute (cached)

If your builds are consistently slower, see Deployment troubleshooting.

Can I deploy on every `git push`?

Yes. Automatic deployments are enabled by default for the branch you pick when creating the service. See Automatic deployments.

Can I roll back to a previous version?

Yes — any successful deployment from the last 90 days can be re-released in seconds without rebuilding. See Redeploy & rollback.

What happens to my live service if a build fails?

Nothing. Failed builds don't touch your live version — the previous deployment keeps serving traffic.

Can I preview a pull request before merging?

Per-PR preview deployments are not supported in v1. The common workaround is to create a second service that tracks your staging or develop branch.

Can I trigger a deployment from my own CI?

Not yet via a public API. For now, deployments are triggered by pushes to your tracked branch or by clicking Deploy in the dashboard. A public API is on the roadmap.

Configuration

Where do I set environment variables?

Service → Environment Variables tab. Variables apply on the next release. See Environment Variables.

Are environment variables encrypted?

Yes. Stored encrypted at rest, decrypted only when applied to your service at runtime.

Can I use a custom Dockerfile?

Yes. Add a Dockerfile at your repo root and Inhank Cloud will use it instead of auto-detecting. See Supported runtimes.

What port should my app listen on?

The port from the PORT environment variable (defaults to 8080). Don't hard-code a port — read process.env.PORT (or your language's equivalent). See Deployment troubleshooting.

Custom domains

Is HTTPS automatic?

Yes. Every custom domain gets a free, auto-renewing Let's Encrypt certificate. You don't configure or renew anything.

Do you support wildcard domains?

Not yet — wildcard certificates require a different ACME challenge (DNS-01) that isn't yet supported. Add each subdomain explicitly.

Can I use Cloudflare in front of my service?

Yes. After your domain is verified and the certificate is Active, you can enable Cloudflare's proxy (orange cloud) for CDN / WAF. During initial verification, keep it set to DNS only (grey cloud). See Custom Domains.

Can I bring my own SSL certificate?

Not yet. We only issue Let's Encrypt certificates.

How many custom domains can a service have?

Up to 10 per service. Email us if you need more.

Resources & scaling

What CPU and memory does my service get?

It depends on the plan you pick. Default is Starter (1 vCPU / 1 GiB RAM). See Resource usage.

What happens if I hit the memory limit?

Inhank Cloud restarts the affected instance automatically. If you have multiple instances, the others keep serving traffic during the swap.

Can I run multiple instances of my service?

Yes — set instance count up to 20 from Service settings → Scaling. Useful for higher traffic and improved availability. See Resource usage: scaling.

Can I pause a service without deleting it?

Yes — set instance count to 0. The service stops running and you stop paying for runtime, but the plan still renews. To completely stop billing, delete the service.

Do you autoscale based on traffic?

Not yet. Scaling is manual today. Auto-scaling is on the roadmap.

Logs

How long are logs retained?

Build logs: 30 days
Runtime logs: 7 days

Can I export logs to my own system?

You can download up to 10,000 lines at a time as .txt or .jsonl from the dashboard. Streaming exports to external systems (Datadog, Loki, S3) are on the roadmap.

Why are my logs not showing up?

Most common cause: your app writes to files instead of stdout/stderr. Switch to stdout. See Logs: debugging.

Billing

What does Inhank Cloud cost?

You pay per plan, charged every 30 days from your prepaid wallet. 1 credit = ₹1. The dashboard shows the exact period cost for each plan in Service settings → Plan. Public pricing is on the pricing page.

What's the smallest top-up?

₹100.

Do credits expire?

No. Once added, credits remain in your wallet indefinitely.

What happens if my wallet runs out?

Your services are paused at the next renewal date (instances scale to 0, URLs return 503), but no data is lost. Top up and click Resume to bring them back. See Plans & renewal.

Can I get a refund?

Within 7 days of a top-up: yes, full refund of unused balance. After 7 days: case-by-case. Credits earned via referrals or bonuses are non-refundable. See Invoices: refunds.

Do you support international payments?

Today Razorpay processes the payment; international cards usually work but may be declined by some banks. International tax invoicing isn't yet fully supported.

Can I get an invoice with my GSTIN?

Yes. Add your GSTIN under Settings → Billing profile before topping up, and the receipt will include it. For consolidated monthly invoices, contact us. See Invoices.

Account

Team accounts and shared services aren't yet supported in v1. On the roadmap. For now, services belong to a single account.

How do I delete my account?

Email support@inhank.com. We delete the account and all associated data within 30 days.

Can I change my account email?

Yes — Settings → Account. We'll send a verification link to the new address.

Platform & limits

What languages do you support?

Node.js, Python, Go, Ruby and anything with a custom Dockerfile. See Supported runtimes.

Do you support background workers / cron jobs?

Yes for long-running workers — create a separate service from the same repo and set its start command to start the worker. Scheduled jobs (cron) aren't yet a first-class feature. The workaround is a worker that schedules its own work using a library like node-cron / apscheduler.

Open the dashboard

On this page