Documentation Index
Fetch the complete documentation index at: https://docs.nearbase.dev/llms.txt
Use this file to discover all available pages before exploring further.
Overview
An instance class defines the CPU and memory allocated to your database. Nearbase offers three tiers: Economical, Basic, and Dedicated.Class Code Format
Instance class codes follow this pattern:| Segment | Meaning |
|---|---|
pg | PostgreSQL engine |
{tier} | n1e = Economical · n2 = Basic · n4 = High-Perf · x8 = Dedicated |
{size} | small, medium, large, xlarge, etc. |
{variant} | vCPU and memory variant within the size class |
pg.n2.1c.1m is a Basic instance with 1 vCPU and 1 GB memory.
Tiers
Economical (pg.n1e.*)
Economical (pg.n1e.*)
Entry-level instances at the lowest price point. Suitable for development,
staging, and low-traffic production apps.Best for: Side projects, internal tools, low-traffic apps, dev/test environments.
Basic (pg.n2.* / pg.n4.*)
Basic (pg.n2.* / pg.n4.*)
General-purpose and high-performance burstable instances. Balanced CPU and
memory for most production workloads.Best for: Production web apps, APIs, moderate-traffic SaaS workloads.Available in all 10 Nearbase regions.
Dedicated (pg.x8.*)
Dedicated (pg.x8.*)
Dedicated CPU instances with high memory-to-CPU ratio (8 GB RAM per vCPU).
Designed for CPU-intensive queries, analytics, and latency-sensitive workloads
that cannot tolerate CPU sharing.Best for: Analytics, reporting, high-concurrency production databases,
workloads requiring consistent low-latency query performance.Available in all 10 Nearbase regions.
How to Choose
| Scenario | Recommended Tier |
|---|---|
| Development / staging environment | Economical |
| Low-traffic production app | Economical / Basic |
| Standard web app or API backend | Basic |
| High-concurrency or latency-sensitive | Basic (n4) / Dedicated |
| Analytics / reporting queries | Dedicated |
| Large dataset, CPU-intensive workload | Dedicated |