Staxa

staxa.dev · Compute · 1 record · JSON

Staxa Compute

caveatemailno cardDper-object-cap

staxa.dev/ · cloud VM · compute/staxa · JSON · compare

Free tier	Free plan is a sandbox: '$0 - Tenants included 2 - Services per tenant 2 - Sizes Small - Concurrent builds 1 - Private registries 0 - Network rules per tenant 0 - Custom domains No - Extra tenant USD 5/mo'. Paid plans start at 'USD 49/month'. A tenant is an app, a database, a subdomain and TLS in its own Kubernetes namespace. unit none; metered on wall-clock; free-forever
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	email not published
Limits	per-object-cap each tenant is one 'Small' tier, which the API documentation's example payload puts at a 500m CPU limit, 512Mi memory limit and 5Gi storage, and the free plan allows two of them with no custom domains. source each tenant is one 'Small' tier, which the API documentation's example payload puts at a 500m CPU limit, 512Mi memory limit and 5Gi storage, and the free plan allows two of them with no custom domains.
Binding	per-object-cap each tenant is one 'Small' tier, which the API documentation's example payload puts at a 500m CPU limit, 512Mi memory limit and 5Gi storage, and the free plan allows two of them with no custom domains.
Interface	rest inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	two isolated namespaces, each with its own database and TLS, is enough to run a staging and a production copy of one small service, which most free tiers refuse to give as two separate environments.
Reliability	no reliability event recorded
Notes	The /pricing route is login-walled: broker read returned exit 1 with 'the origin sent the read to its sign-in page'. Routes tried: read /pricing (login wall), archive /pricing at 2026-09 (no capture; Wayback and Cloudflare scan both empty), search on the site name, which returned the pricing table text verbatim. The free tier numbers are quoted from the indexed text of the vendor page, not from a live render. Tier sizes are not published as a table; the 500m / 512Mi / 5Gi shape comes from the API documentation's example payload and is indicative.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21

Evidence (3)

date	source	what it proved
2026-10-22	staxa.dev/	pricing table text returned by the search index for the site: 'Free ... $0 Sandbox plan - Tenants included 2 - Services per tenant 2 - Sizes Small - Concurrent builds 1 ... Custom domains No ... Extra tenant $5/mo', quoted
2026-10-22	staxa.dev/	'The Free plan includes 2 tenants. Paid plans from $49/month.', quoted
2026-10-22	staxa.dev/docs	'resource_size: Resource tier: small, medium, large' with default 'small'; the documented tenant payload shows cpu_limit '500m', memory_limit '512Mi', storage_limit '5Gi' for a small tenant

More fields (1)

{
 "wave2": {
  "class": "new-provider",
  "free_tier_kind": "free-forever",
  "shape": {
   "vcpu": 0.5,
   "ram_gib": 0.5,
   "gpu_class": null,
   "gpu_count": null
  }
 }
}

Unknown or withheld values (9)

$.egress.metered egress-unknown
$.egress.terms not-stated
$.identity_cost.detail process
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable
$.tooling not-stated