Core concepts

A short reference for the terms used across the dashboard and these docs.

Service

A service is one deployable application — backed by one Git repository and one branch. It is the main thing you create and manage in Inhank Cloud.

A service owns:

• Its deployments
• Its environment variables
• Its custom domains
• Its runtime instances and logs
• Its plan and billing

If you have multiple apps (a web app, an API, a worker), create one service per app — they can share the same repository.

Deployment

A deployment is a single attempt to build and release a specific commit of your service. It has:

• A status (Queued, Building, Releasing, Live, Failed)
• A build log
• A commit hash and message
• A release timestamp (if it goes live)

Each service keeps a history of all its deployments. You can redeploy or roll back to any previous successful deployment at any time.

Build

A build is the phase of a deployment that turns your source code into a runnable application package. During the build, Inhank Cloud:

• Detects your language and framework
• Installs dependencies
• Runs your build step, if any (e.g. npm run build)
• Packages everything for running

You can follow a build's progress live, or read its log after it completes.

Instance

An instance is one running copy of your service. By default, each service runs one instance. You can scale up to run several in parallel, which spreads traffic and increases availability. See Resource usage.

Environment variable

A piece of configuration available to your app at runtime — typically a database URL, API key, or feature flag. Stored encrypted, edited from the dashboard's Environment Variables tab.

See Environment Variables.

Domain

A hostname your service responds on. Every service starts with a free default domain (<service-name>.inhank.app). You can add one or more custom domains (e.g. app.example.com) with verified DNS and automatic HTTPS.

See Custom Domains.

Logs

The text your service writes while building (build logs) and while running (runtime logs). Available in the dashboard with live tail, search, and export.

See Logs.

Plan

A plan sets your service's resource limits and monthly cost. Plans renew every 30 days by deducting credits from your wallet.

See Billing.

Wallet

Your wallet holds prepaid credits (1 credit = ₹1). Plan renewals and any usage-based charges are deducted from your wallet. You top it up from the Billing screen.

See Billing.

Lifecycle summary

To bring everything together:

Repository ──► Service ──► Deployment ──► Build ──► Instance(s)
                                                       │
                                                       ▼
                                                Domain + HTTPS
                                                Logs
                                                Resource usage

Your wallet funds the plan that determines what resources each service's instances run with.