Compute Inventory

POS-related EC2 instances only. Other Alberaber products (alberaber-erp-tsf, alberaber-infra) are filtered out.

Monthly POS spend

$72.49on-demand

2 hosts · 1 pool + 1 ops

After Kahve cutover

$72.49/mo

Net delta: $0 · Kahve lands on pool-1 (no new host needed yet)

vs Supabase Cloud Pro

↓ $$

Roughly 70% cheaper than equivalent Cloud projects at our scale.

evrenos-pool-1TENANT POOL

i-0f09a2a79054c6f38

$56.06/mo OD

on-demand

Instance
t4g.large
vCPU
2
RAM
8 GB
AZ
eu-central-1a
Tenants on host
1
CPU now
Memory now
Status
ACTIVE
Source of live metrics
Prometheus · evrenos-pos-selfhosted
Tenants today
evrenos-test
Tenants planned (after Kahve cutover)
evrenos-testkahve (new)
Why this host exists

Single tenant pool — hosts dev + production tenants together. Today: evrenos-test (dev/staging used to simulate paid workloads). At Kahve cutover: + kahve (production). Split into a dedicated prod pool only when 2nd paying customer onboards OR memory sustained > 75% for 1 h.

evrenos-ops-01OBSERVABILITY

i-04155f702675e42e9

$16.43/mo OD

on-demand

Instance
t4g.small
vCPU
2
RAM
2 GB
AZ
eu-central-1a
Tenants on host
0 (infra only)
CPU now
Memory now
Status
ACTIVE
Source of live metrics
no node-exporter (infra-only)
Why this host exists

Loki + Prometheus + admin dashboard backend for the entire POS fleet. No tenant traffic; serves operators only. Separated from pool-1 so observability stays up when pool-1 is under stress (the moments you most need to see logs).

When to split into a dedicated prod pool

We deliberately did not provision prod-pool-1 yet. Triggers that would change that decision:

  • 2nd paying customer onboards (blast-radius matters)
  • pool-1 memory sustained > 75% for 1 h
  • pool-1 swap usage detected during business hours
  • Compliance audit demands physical isolation
  • You want to do heavy dev experiments without affecting Kahve

Until one of these is true, we stay lean at 2 hosts ($72.49/mo OD).