Skip to main content

​
Overview

An instance class defines the CPU and memory allocated to your database. Nearbase offers two groups: General Purpose and Dedicated. Pricing is uniform across every region — the same class costs the same everywhere.

​
Class Code Format

Instance class codes follow this pattern:
For example, pg.n4.4c.1m is a General Purpose instance with 4 vCPU and 16 GB memory.

​
Catalog

​
General Purpose

Balanced CPU and memory for most workloads. Includes low-cost economy (ARM) options for small apps and trials. Best for: Side projects, dev/test, internal tools, production web apps, APIs, and moderate-traffic SaaS workloads.
Economy instances (pg.n1e.* / pg.n2e.*) are ARM-based and may not be available in every region — pg.n1e.* in particular is not available in ap-northeast-1 (Tokyo), ap-southeast-3 (Kuala Lumpur), and ap-southeast-7 (Bangkok). Availability is validated when you create an instance; pick a Standard or Dedicated class in those regions.

​
Dedicated

Dedicated CPU instances with a 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.

​
How to Choose

​
Scaling

You can change your instance class at any time from the instance detail page. Scaling is handled by the platform with minimal interruption. Your billing is adjusted on a prorated basis for the remainder of the billing period.
Start with a smaller class and scale up as needed. Nearbase supports vertical scaling without data migration.