This page lists answers to questions that many folks have as they're getting up and running with Render.

## Languages and technologies

### Which languages does Render support?

Render [natively supports](/content/docs/language-support/index.html) **Node.js** / **Bun**, **Python**, **Ruby**, **Go**, **Rust**, and **Elixir**.

You can deploy an app in virtually _any_ language (.NET, Java, PHP, etc.) via a [Docker image](/content/docs/docker/index.html).

### Which datastores does Render support?

Render offers managed [Postgres databases](/content/docs/postgresql/index.html), along with [Key Value instances](/content/docs/key-value/index.html) that are compatible with virtually all Redis clients.

You can also run your own custom database instance (MariaDB, MongoDB, etc.) backed by a [persistent disk](/content/docs/disks/index.html).

## Billing

### What can I do on Render for free?

See [Deploy for Free](/content/docs/free/index.html).

### What does Render bill for?

Render bills each workspace monthly for the items listed below. For details on all of these, see the [pricing page](/content/pricing/index.html).

| Billable | Description |
| --- | --- |
| ###### Workspace plan | Each workspace has an associated plan: **Hobby**, **Pro**, **Scale**, or **Enterprise**. This plan determines the workspace's [features](/content/docs/platform-features-by-plan/index.html), limits, and monthly fee.<br>The **Hobby** plan does not have a monthly fee. See the fees for other plans on the [pricing page](/content/pricing/index.html). |
| ###### Compute and storage costs | Prorated by the second. If a service is active for ten seconds in a given month, you are billed only for those ten seconds.<br>You are billed for each of the following:<br>- Each [paid instance](/content/pricing#compute/index.html) of a service or datastore<br>  <br>  - For [scaled](/content/docs/scaling/index.html) services, you are billed for each running instance.<br>  - This includes paid instances running as part of a [service preview](/content/docs/service-previews/index.html) or [preview environment](/content/docs/preview-environments/index.html).<br>- Database replicas created for Render Postgres [high availability](/content/docs/postgresql-high-availability/index.html) or [read replicas](/content/docs/postgresql-read-replicas/index.html)<br>- Storage capacity for Render Postgres databases and persistent disks |
| ###### Pipeline minutes | **Includes a monthly included amount.**<br>Render's [build pipeline](/content/docs/build-pipeline/index.html) is responsible for building your project before it's deployed. This includes running each service's [build and pre-deploy commands](/content/docs/deploys#deploy-steps/index.html). Each workspace receives a monthly included amount of pipeline minutes (see the [pricing page](/content/pricing/index.html)), which are consumed while running these commands.<br>Render also offers a [performance pipeline tier](/content/docs/build-pipeline#pipeline-tiers/index.html) for teams with builds that require additional memory and/or CPU. Performance pipeline minutes carry an additional charge and do _not_ provide a monthly included amount.<br>You can set a monthly [spend limit](/content/docs/build-pipeline#setting-a-spend-limit/index.html) for pipeline minutes. If you reach this limit in a given month, _Render stops running new builds for your services until the next billing period_. |
| ###### Outbound bandwidth | **Includes a monthly included amount.**<br>Outbound bandwidth includes all network traffic sent by your services to destinations outside of Render. This data includes web pages, API payloads, and so on.<br>Each workspace receives a monthly included amount of outbound bandwidth shared across all services (see the [pricing page](/content/pricing/index.html)). If you exceed this, Render bills you for a supplementary amount.<br>_Inbound_ bandwidth (traffic _to_ your services) is free. As part of Render's [DDoS protection](/content/docs/ddos-protection/index.html), Render does _not_ bill for bandwidth usage incurred from a DDoS attack. |
| ###### Custom domains | Each plan includes a set number of [custom domains](/content/docs/custom-domains/index.html) across all services. Additional domains cost $0.25 each per month. See the [pricing page](/content/pricing/index.html) for included amounts by plan. |

### All of my services run on free instances. Can I still be billed?

**Yes, if you've added a payment method.** If you exceed your monthly included amount of outbound bandwidth or build pipeline minutes, Render bills you for a supplementary amount. You can set a monthly [spend limit](/content/docs/build-pipeline#setting-a-spend-limit/index.html) for pipeline minutes.

If you haven't added a payment method and you would incur charges, Render instead disables your services for the duration of the current billing period.

## Service behavior

### My app runs fine locally. Why does it fail to deploy?

Please see [Troubleshooting Your Deploy](/content/docs/troubleshooting-deploys/index.html).

### Why is my free service sometimes slow to respond?

Free web service instances [spin down](/content/docs/free#spinning-down-on-idle/index.html) if they receive no incoming traffic for 15 consecutive minutes. These services take about a minute to spin back up when they next receive a request.

Paid compute plans do _not_ spin down.

Learn more about [free instance limitations](/content/docs/free/index.html), including for Render Postgres and Key Value.

### Why do files saved to my service's filesystem disappear?

By default, Render services have an **ephemeral filesystem**, which means that any changes you make to local files are _lost_ every time a service redeploys or restarts.

For long-term data storage on Render, we recommend one of the following:

- For storage of relational data, create a [Render Postgres database](/content/docs/postgresql/index.html).
- For storage of key-value data, create a [Render Key Value instance](/content/docs/key-value/index.html).
- For storage of arbitrary files, attach a [persistent disk](/content/docs/disks/index.html).

- You can also use a persistent disk to run a custom database instance instead of Render Postgres, such as [MySQL](/content/docs/deploy-mysql/index.html).

### Can I deploy multiple apps to a single Render service?

**It might be possible, but you shouldn't.** Run each of your applications in a separate service to ensure proper resource isolation for security and performance.

Let's say you want to deploy an architecture consisting of a frontend site, a backend API, and a datastore. We recommend deploying these as follows:

| App | Service type(s) |
| --- | --- |
| Frontend site | [Static site](/content/docs/static-sites/index.html) or [web service](/content/docs/web-services/index.html) |
| Backend API | [Web service](/content/docs/web-services/index.html) or [private service](/content/docs/private-services/index.html) |
| Datastore | [Render Postgres](/content/docs/postgresql/index.html) or a custom database backed by a [persistent disk](/content/docs/disks/index.html) |

To help identify which service types are right for your use case, see [this flowchart](/content/docs/service-types#which-service-type-is-right-for-my-code/index.html).

## Account administration

### Can I transfer existing services from one workspace to another?

No, it is not currently possible to transfer existing services between workspaces. Instead, you can:

- [Invite team members](/content/docs/team-members/index.html) to collaborate on services in your current workspace
- Recreate your services in the workspace you want to move them to

## Render support

### Which types of issues can Render's support team help with?

Please see [When to contact support](/content/docs/troubleshooting-deploys#when-to-contact-support/index.html).