# How Sliplane works

Source: https://docs.sliplane.io/introduction/concepts

Learn how Sliplane works and how it can help you to focus on shipping instead of managing your servers.

Sliplane runs applications, managed PostgreSQL databases and S3-compatible storage. Deploy code from GitHub or images from container registries; Sliplane manages builds, deployments and servers.

> **Simple Pricing**
>
> Run multiple services for one **per-server** price. Managed databases and Object Storage are billed separately. [Billing and pricing](/teams/billing)

[Services](/services/deploying-a-service)

Deploy your first service from GitHub or a registry, with or without a Dockerfile

[Servers](/servers/create-a-server)

Learn how to create servers in Sliplane

[Object Storage](/object-storage/getting-started)

Store files and uploads in S3-compatible buckets managed through Sliplane

[Databases](/databases/overview)

Managed PostgreSQL databases with backups, metrics, and access control

## FAQ

### How much does Sliplane cost?

Sliplane charges per server. Host unlimited services for one price. See the [pricing page](https://sliplane.io/pricing) for current rates and the [billing guide](/teams/billing) for how charges work.

### Where are my servers hosted?

Servers in Germany and Finland run on infrastructure from [Hetzner GmbH](https://hetzner.com). Servers in the US and Singapore run on Datapacket and Latitude.

### Can I bring my own server?

No. Sliplane runs on managed infrastructure; you cannot install its agent on your own servers.

### Why should I use Sliplane?

Sliplane handles builds, deployments and server management so you can run applications without maintaining the infrastructure.

### Do I need to know Docker to use Sliplane?

No. You can deploy straight from a GitHub repository without writing a Dockerfile — Sliplane detects your application's stack and builds it for you using [Railpack](https://railpack.com/). If you do want full control over the build, you can add a Dockerfile and Sliplane will use it instead.

### How do I get started?

Head over to [Sliplane](https://sliplane.io) and sign up with your GitHub account.

## Core concepts

### Teams

[Teams](/teams/getting-started) group resources under one billing account and let you share access with collaborators.

### Projects

[Projects](/projects/getting-started) group related services, such as an application's frontend, backend and workers.

### Servers

[Servers](/servers/create-a-server) run services. Each server has its own charge and can host as many services as its resources allow.

### Services

A [service](/services/deploying-a-service) is an application running on a server with its configuration. Deploy it from GitHub, with or without a Dockerfile, or from a container registry.

### Object Storage

[Object Storage](/object-storage/getting-started) provides S3-compatible buckets for files, uploads and backups.

## Ways to use Sliplane

### Dashboard

Use the [dashboard](https://sliplane.io/app) to deploy services and manage resources, teams and billing.

### API

Use the [API](https://ctrl.sliplane.io) to automate resource management. Create a team [API key](/teams/api-keys) to get started.

### MCP

The [MCP server](/mcp/getting-started) lets AI coding tools work with Sliplane.