The previous version’s API gateway supported REST and basic GraphQL. The updated version goes much further with GraphQL federation. This means you can now combine multiple Neobit workflows and external services into a single, unified GraphQL endpoint.
For enterprises running dozens of microservices, this feature alone justifies the upgrade. The federated gateway also includes automatic persisted queries (APQ) and query cost analysis to prevent DDoS or resource exhaustion.
With any major update, pricing questions arise. The good news: the Neobit 11 updated version follows the same tiered model as before, but with adjusted quotas: neobit 11 updated
Existing customers on annual plans receive the updated version at no additional cost until their renewal date.
You asked, we listened. The number one feature request from our community was better file/asset organization. The previous version’s API gateway supported REST and
The "Neobit" era is seeing a reduction in the number of players.
We ran a series of tests comparing the previous stable build (Neobit 11.2.4) against the Neobit 11 updated version (build 11.3.0). All tests were run on identical hardware (4 vCPU, 16GB RAM, standard SSD). Existing customers on annual plans receive the updated
| Metric | Neobit 11.2.4 | Neobit 11 Updated (11.3.0) | Improvement | |--------|---------------|-----------------------------|--------------| | Workflow cold start (container) | 1,200 ms | 340 ms | 71% faster | | Parallel task throughput (100 tasks) | 42 tasks/sec | 89 tasks/sec | 112% higher | | Memory footprint (idle) | 480 MB | 210 MB | 56% reduction | | API gateway latency (p99) | 180 ms | 62 ms | 65% lower | | Secret retrieval time | 210 ms | 18 ms (Vault cache) | 91% faster |
These numbers confirm that the Neobit 11 updated release is not just a feature drop—it is a serious performance upgrade.