Getting Started

Introduction

What Appentic is, how it fits into your workflow, and what to read next.

Appentic is a deployment platform for developers who want to ship web apps, APIs, and background services without having to become full-time cloud operators. You connect a GitHub repository, pick a machine size, and Appentic takes it from there: building your code, running it on managed infrastructure, handing you logs and metrics, and renewing TLS certificates in the background.

It's built around the workflow you already have. Your code stays in GitHub, your builds run on every push, and the primitives you'd reach for on any other cloud (HTTP services, PostgreSQL, Redis-compatible caches, workers, cron jobs) are all here, wired together so the boring parts stay out of your way.

What Appentic optimises for

Appentic is opinionated where it needs to be and invisible where it should be. The guiding idea is that a developer shouldn't have to open a cloud console to do something routine.

  • Git-driven deploys. Every push to your default branch becomes a deploy. No separate CI to wire up, no deploy scripts to maintain.
  • Managed data. PostgreSQL and a Redis-compatible key-value store are one click away, and their credentials are injected into your services as environment variables, so you don't copy connection strings into secrets managers.
  • Operable by default. Real-time logs, metrics, and a web shell are built in. You can tail a log, check p95 latency, or psql into your database without installing a single extra tool.
  • Usage-based pricing. You pay for the compute, storage, and bandwidth you actually use. No per-seat fees, no plans to upgrade, and services can scale to zero when idle.

How this documentation is organised

The sidebar on the left is grouped so you can read top to bottom as a tutorial, or dip in when you're debugging something specific.

Getting help

If something isn't covered here, email support@appentic.com or sign in to app.appentic.com and open a support ticket from the dashboard. Bug reports and documentation feedback are both welcome.