Installed and run by the customer
A copy handed over to run on the customer's own infrastructure, with the vendor losing visibility into how it is used afterward.
TEZZ · API ACCESS
A request in, a result out, nothing installed
API access means a platform sends TEZZ a request and gets a result back, the way a checkout page sends Stripe a payment request without ever running Stripe's own servers. Nobody installs TEZZ, runs it on their own infrastructure, or receives a copy to operate independently.
Customers connect via API, never by deploying it. That has held since TEZZ entered training and is not a limitation added later.
THE RANGE OF PRACTICE
What deployed looks like, and what API-only looks like
Described by behaviour, not by a score.
A closed product with no visible boundary
Access granted, but no clear statement of where the system runs or how data is isolated between accounts.
A request in, a result out, nothing installed
The system runs on infrastructure it was built for, reached through a defined interface rather than handed over.
WHERE WE SIT
API-only, by design, not by limitation
Keeps the data isolation described in the architecture page intact.
TEZZ runs on Gigagrams’ own systems only, reached through a platform's own API, not sold as a general API product. AI projects for clients are separate: built to Gigagrams protocols, zero trust, human in the loop, multi-agent.
STRAIGHT ANSWERS
Questions about API access
The ones that come up before anyone signs anything.
A platform we build sends TEZZ a request and gets a result back, the same way a checkout page sends Stripe a payment request without ever running Stripe's own servers. Nobody installs TEZZ, runs it on their own infrastructure, or gets a copy of it to operate independently.
TEZZ runs on Gigagrams’ own systems only. AI projects for clients are separate, built to our protocols. Keeping TEZZ API-only keeps the data isolation and training boundaries intact, which get harder to guarantee the moment a system is handed off to run outside our own infrastructure.
Yes, from within a Gigagrams platform, through that platform’s own API, rather than as a general-purpose API sold on its own.
No. The request and response pattern is how most production AI features work day to day, regardless of vendor. What API-only actually restricts is who can run TEZZ independently, not how a platform built on it functions for the end user.
Building on a Gigagrams platform and want TEZZ involved?
Tell us what you are building and we will scope how it connects through the platform's own API.