Home
Heroic Labs
heroiclabs.com · 2 records in Compute, Storage · JSON
Records 2
heroiclabs.comPlatform hostcompute/heroic-labsJSONcomparereport an error
- Free allowance
- Not stated
- Verdict
- paidno free allowance; listed for its price
- Cost
- no price stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- write-gatedno plan and no price: the hosted product is reached by signup, and the framework itself is open source a user runs
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | not stated unit none; metered on wall-clock |
|---|
| Price | none stated |
|---|
| Limits | - write-gated (binding) no plan and no price: the hosted product is reached by signup, and the framework itself is open source a user runs source
|
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | unknown |
|---|
| Reliability | no reliability event recorded |
|---|
| Evidence note | documented the site was read on 2026-10-22 and presents an open-source backend with a managed cloud signup. No plan or price appears, which confirms paid-only for the hosted product and leaves the open-source half as software |
|---|
| Parsed numbers | |
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-02 | heroiclabs.com | not published |
| 2026-10-22 | heroiclabs.com | 'Nakama: the hugely popular open source game backend framework' with 'Take back control of your game backend and own your data' and a Heroic Cloud signup, quoted; no plan and no price on the page |
More fields 4
| keep rate basis | no field in the source |
|---|
| billing model | unclassified |
|---|
| free tier kind | none |
|---|
| reclassified from | dead |
|---|
Unknown values 11
- chaining: a source was read and is silent on this field
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- free tier stated: a source was read and is silent on this field
- interface: the access interface was not established
- limits note: a source was read and is silent on this field
- per object cap stated: a source was read and is silent on this field
- reliability note: nothing of this kind was observed
- retention notes: the field may be stated in a source that was not read
- retention stated: a source was read and is silent on this field
- tooling: a source was read and is silent on this field
forum.heroiclabs.com/t/storage-max-size-in-megabytes/3459storage/nakama-heroic-cloud-storage-engineJSONcomparereport an error
- Free allowance
- Storage objects are jsonb rows in Postgres — 'theoretically store up to 255 megabytes' but Heroic Labs explicitly advises against it ('we don't guarantee it will perform well at scale').
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Storage objects are jsonb rows in Postgres — 'theoretically store up to 255 megabytes' but Heroic Labs explicitly advises against it ('we don't guarantee it will perform well at scale'). No unit none; metered on none |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not recorded |
|---|
| Interface | unknown |
|---|
| Tooling | not recorded |
|---|
Evidence 1
More fields 1
| dead end | {"failure_class": "quota","why": "Storage objects are jsonb rows in Postgres — 'theoretically store up to 255 megabytes' but Heroic Labs explicitly advises against it ('we don't guarantee it will perform well at scale'). No","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field