Skip to content
Host Little logo markHost Little

Next.js hosting and PostgreSQL. One clear path.

Connect GitHub, release a Node.js application, and add PostgreSQL where it is approved for your project. The path stays legible from source to production.

Deploy an appSee the Next.js path
  • GitHub to Next.js
  • Managed PostgreSQL
  • Domains and HTTPS

Source to release

Health gates traffic

  1. GitHub source

    A repository and branch

  2. Isolated build

    An admitted release artifact

  3. Healthy release

    Traffic follows the health check

PostgreSQL alongside the appCreate, connect, and meter usage
Explore the boundary

Agent-written code still deserves a normal release path.

  • ChatGPT
  • Cursor
  • Claude
  • Antigravity
  • GitHub Copilot

One project, in the order it actually happens.

A deploy is a sequence of decisions, not a pile of unrelated cloud products. Host Little keeps that sequence visible from source through delivery, then makes room for the database path when the project needs it.

  1. Connect GitHub

    Start with a GitHub-hosted Node.js or Next.js HTTP application.

    Next.js Hosting

  2. Build a release

    Keep the application path legible before adding more infrastructure around it.

    App Hosting

  3. Add PostgreSQL

    Create a standalone database or attach one to the app with the same usage wallet.

    Database Hosting

  4. Deliver the app

    Custom domains and HTTPS belong beside the application, not in another control plane.

    Domains and HTTPS

The current launch focus is the GitHub to Next.js application path. More runtimes and broader database availability should arrive as verified product capability, not as a marketing promise first.

The handrails are part of the product.

You should not need a decoder ring to understand how source becomes a release, when it receives traffic, or where the delivery settings live. That clarity is the starting design constraint for the public site and the portal.

Source stays attached

The supported path begins with a GitHub repository and branch, not a hand-built deployment scene.

Traffic has a gate

A release earns production traffic after its health check, so a completed build is not confused with a healthy app.

Delivery stays with the app

Custom domains and HTTPS belong beside the release path instead of in a separate control-plane scavenger hunt.

Usage has a boundary

Measured resource use and workspace spend controls keep the commercial side legible as the project grows.

PostgreSQL without another control plane.

Create it alone or beside an app. Copy a pooled TLS connection, pay for measured use, and let idle compute scale away without losing durable data.

See Database Hosting scope

Small by default

Start at 0.25 CU with a five-minute idle timeout, then raise the compute ceiling when the application earns it.

Protected connection path

App bindings use protected references, while the workspace owner controls connection reveal and credential rotation.

Honest product boundary

Backups and isolated restores are available. We do not sell automatic HA, read replicas, multi-region, or broad branching as launch features.

Pricing that stays legible.

Developer is $5 a month. Pro is $20. The plan payment becomes credit against measured resource use, and each workspace has a spend boundary.

Developer

For side projects and lean production apps

$5/month

Plan capacity

  • 1 app
  • 0.5 vCPU · 1 GB RAM
  • 500 GB bandwidth
Start Developer

Pro

For production apps that need more headroom

More headroom

$20/month

Plan capacity

  • 1 app
  • 2 vCPU · 4 GB RAM
  • 2 TB bandwidth
Choose Pro

Included with both plans

  • GitHub-hosted Node.js and Next.js HTTP apps
  • Managed PostgreSQL from the same usage wallet
  • Domains, HTTPS, logs, and runtime measurements
See resource rates and spend-limit details

Frequently asked questions

What can I deploy?

Deploy from a GitHub repository with Railpack, or choose a public Linux amd64 Docker or OCI image from Docker Hub, GitHub Container Registry, Quay, or GitLab Container Registry. Image-source apps listen on PORT=3000 at 0.0.0.0.

How do the monthly plans work?

Developer is $5/month and Pro is $20/month. 100% of your plan payment becomes non-rollover usage credit for that month, applied to measured compute, storage, and database usage.

What does the launch credit include?

Developer charges $5 when checkout succeeds. Eligible new Developer accounts then receive a one-time $5 launch credit in addition to that month's plan credit. Monthly and launch credits do not roll over.

What usage is metered?

App Cloud meters CPU at $20/vCPU-month, memory at $10/GB-month, persistent storage at $0.15/GB-month, and outbound transfer at $0.03/GB. App usage uses recorded runtime measurements; PostgreSQL compute uses its enforced allocation. Usage is prorated.

Is PostgreSQL database hosting available yet?

Database Hosting is currently limited to approved DB Alpha beta and internal workloads. Public self-service provisioning, connection reveal, and the portal Workbench remain gated while the launch proof is completed. The approved path supports protected connections, encrypted logical backups, restore copies, and bounded read-only Workbench queries; it is not a public plan entitlement yet.

Which regions can I choose?

AWS App Hosting launches in US East. Existing regional workloads remain visible in their current Host Little regions during migration.

How does the workspace spend limit work?

Set a monthly workspace spend limit in Billing. The recorded ledger can trail live activity, so usage may cross the displayed limit before reconciliation. At the limit, the app stops and PostgreSQL access is removed while Aurora becomes eligible to auto-pause after its idle window. Observed compute and persistent storage can continue accruing.

What can I manage from a project?

Project pages expose deployments, redacted runtime logs, CPU and memory metrics, custom HTTPS domains, environment variables, and source controls. Database workspaces add secure connection reveal, usage, lifecycle controls, backups, and an SQL workbench.

What can I take with me?

Your GitHub source or public container image and domain remain under your control. Approved database beta workspaces can use the owner-only TLS connection and pg_dump before deletion. Public database provisioning and export access are not enabled for general self-service yet.

Start with the repository you already trust.

Launch a focused GitHub to Next.js application, create PostgreSQL beside it, and keep both inside one usage wallet.

Deploy an appSee pricing