Platform

Batteries included.

A runtime is only as useful as what it ships with. Grid arrives loaded — the catalog, signed vertical packs, package trust across seven ecosystems — and the NS protocol is how “loaded” becomes an ecosystem.

The catalog.

2,816 built-in functions across 51 categories — from Excel-compatible math to logistics, healthcare, real estate, geospatial, and computational biology. The batteries most products sell as add-ons.

ships today

Domain packs.

A vertical starter kit as a signed artifact, not a template folder: contracts, data profiles, experiences, governance, AI policy, migrations, and qualification fixtures. Real estate ships complete; eight more verticals ship fitness-profiled.

ships today

Package federation.

gridctl package add turns exact npm, PyPI, NuGet, Maven, crates.io, Go, and vcpkg coordinates into verified extension capsules with typed projections — seven ecosystems, one trust model.

ships today

Extensions.

Luau, WASM, and native runners with signed release envelopes, and a Package Center in the desktop app. Extending the engine doesn't mean trusting a random binary.

ships today

APIs as packages.

Import OpenAPI, AsyncAPI, GraphQL, WSDL, or gRPC schemas as immutable, digest-pinned packages whose operations become typed functions — an integration is an artifact, not glue code.

ships today

A signed trust chain.

Descriptor key → instance bundle → policy and publisher keys → catalog decision → release verification. Nothing installs unverified, and every link in the chain is checkable.

ships today

The template marketplace.

The NS protocol's service plane defines a marketplace role: templates and packages served as signed artifacts over the same trust chain, by any conforming provider. The chain ships in the engine today; the storefront is the protocol's next act.

specified in the NS protocol

The service plane.

Licensing, update rings, federation, quotas, and notifications arrive as signed bundle classes from a provider — a neutral contract with conformance profiles, where passing the conformance suite, not marketing, is what makes a provider real.

specified in the NS protocol

An ecosystem is a protocol, not a promise.

NS is a neutral contract with conformance profiles; Grid Cloud is one conforming provider, not the protocol. Conformance is executable — the same suite any provider must pass — so “compatible” is a test result, not a claim.

The full contract lives in the engine's NS specifications.

NextFind your Monday