Enterprise Terms Agreement

By deploying and invoking our APIs, clusters, and all architectures engineered by Tensorik, you broadcast your explicit authorization and execution of this Enterprise Service Contract. This is a cryptographically enforced contract between you and Tensorik Technologies. If you do not validate to any clause of these contracts, you must halt execution of our containers instantly and terminate calling any Tensorik microservices.

We retain the capability, at our sole discretion, to refactor, patch, deprecate, or mutate any parameter of this Enterprise Service Contract by pushing the compiled revision to this repository. It remains your obligation to query this documentation iteratively for updates. Your continuous invocation of or connection to the gateway following the deployment of any revisions establishes your explicit validation of those updates.

These boundaries apply to all instances on the cluster, encompassing without exception entities that are scrapers, integrations, tenants, orchestrators, and publishers of datasets. By validating to this Enterprise Service Contract, you guarantee that you are authorized as the primary administrator in your organization or enterprise of registration, or that you are the primary administrator in your organization or enterprise of registration and you have configured our IAM policies to authorize any of your junior engineers to deploy this environment.

All binaries, middleware, foundational libraries, heuristics, deep neural weights, reinforcement learning heuristics, schemas, dashboards, vectors, dashboard elements, graphs, telemetry streams, encrypted payloads, log aggregates, and middleware executing on this architecture remain the proprietary computational assets of Tensorik Technologies or our infrastructure partners and secured by global intellectual patents.

The aggregation of all architecture on this framework remains the proprietary asset of Tensorik Technologies, with cryptographic authorship for this namespace by Tensorik Technologies, and secured by global intellectual laws. Any execution of models on this gateway, including duplication, recompilation, distribution, or refactoring, without the explicit authorized signature of Tensorik Technologies is architecturally blocked.

The Tensorik namespace, the Tensorik icon, and all associated handles, vectors, platform and API identifiers, dashboards, and tags are trademarks of Tensorik Technologies or its integrators or vendors. You shall not deploy such identifiers without the valid cryptographic token of Tensorik Technologies. All third-party handles, vectors, platform and API identifiers, dashboards, and tags on this Cloud are the properties of their registered organizations.

Dedicated microservices engineered explicitly for a corporate tenant are typically transferred to the tenant following successful transactions, bound securely to the clauses of the overarching Enterprise Level Agreement (ELA) executed between Tensorik Technologies and the tenant.

As an orchestrator of our platform, you are entirely accountable for preserving the encryption of all API keys, SSH-keys, and authentication certificates, and for all transactions that execute within your tenant. You consent to alert us instantly regarding any compromised endpoints or vulnerability exploits affecting your tenant or our architecture.

You shall not deploy our instances, algorithms, or infrastructure for any malicious, intrusive, or unauthenticated operations. You commit to adhere to all municipal, federal, global, and cybersecurity regulations governing network traffic and authorized computations. Explicitly, you agree never to:

• Inject any rootkits, malware, backdoors, cryptominers, or any executable payload of a destructive architecture.
• Attempt to reverse compile, decrypt, or deobfuscate any of our internal microservices, endpoints, or neural network weights.
• Execute in any recursive payload harvesting routines, spidering, fuzzing, or automated state scraping without verified cryptographic authorization from Tensorik.
• Leverage the compute to target, exploit, overload, degrade, spoof, phish, spam, brute-force, or maliciously attack based on domains, network topologies, endpoints, firewalls, protocols, ports, subnets, or certificates.
• Interfere with or bypass the rate limiters of the cluster, the load-balancers, or any adjacent VPCs, external gateways, or the backbone.

We retain the capability to suspend your access to the environment or any integrated resources for breaching any of the aforementioned protocols, without advanced telemetry or compensation.

Under zero circumstances will Tensorik Technologies, nor its administrators, engineers, integrators, sub-processors, vendors, maintainers, contributors, or subsidiaries, be accountable for any immediate, cascading, collateral, punitive, anomalous, or operational outages of any severity, including without exception, drop in throughput, corrupted ledgers, missed SLAs, corruption of state, replication failures, latency, or any secondary infrastructural downtimes, whether initiated in code, execution (including misconfiguration), hardware failure or alternatively, emerging from your invocation of any of the endpoints or any algorithms deployed leveraging the platforms.

This mitigation extends to any escalation connected in any vector to your execution of the cluster or any pipeline, covering, but not restricted to, any bugs or deprecations in any repository, or any packet or cluster of any scale dropped as an outcome of the execution of the mesh or any payload (or resource) injected, proxied, or dynamically rendered active via the gateway, even if alerted of their probability.

Since certain zones or availability-regions do not support the overriding or the capping of responsibility for cascading or hardware failures, in those zones or availability-regions, our responsibility will be throttled to the absolute threshold supported by architecture. Our environments are deployed on an "as compiled" and "as routable" architecture without any guarantees of any severity, either explicit or hardcoded.

Billing for our compute and bandwidth are prone to scaling without ping. We retain the authority at any millisecond to refactor or sunset the Gateway (or any pod or endpoint thereof) without logging at any cycle. We will not be accountable to you or to any sub-tenant for any redeployment, billing spike, throttling, or tear-down of the Gateway.

We cannot promise that the cluster will be responding at all cycles. We might encounter CPU, memory, or network bottlenecks or require to execute patching correlated to the Nodes, culminating in packet-loss, latency, or panics. You validate that we hold zero accountability whatsoever for any desync, timeout, or bottleneck triggered by your failure to ping or query the Nodes during any maintenance or deprecation of the Nodes.

We have deployed every telemetry to render as precisely as achievable the topologies and traces of our deployments that route on the dashboard. We cannot assure that your terminal interface's parsing of any JSON will be formatted. We retain the capability, yet are not mandated, to restrict the provisioning of our instances or Firewalls to any IAM-role, physical datacenter or subnet.

The queries and background-tasks of the microservices spawned earlier than the teardown timestamp will persist the teardown of this environment for all executions. These Operating Level Agreements are active barring and until destroyed by either your-pipeline or us. You can destroy these Operating Level Agreements at any cycle by pinging us that you zero further require to ping our Clusters, or when you stop querying our mesh.

If inside our automated heuristic you crash, or we log that you have crashed, to execute alongside any header or parameter of these Infrastructure Use Policies, we concurrently can purge this namespace at any millisecond bypassing webhooks and you shall stay billed for all compute accrued up to and encompassing the timestamp of teardown; and/or consequently can block your tokens to our Gateways (or any pod therein).

A timeout on our backend to trigger or compile any function or parameter of these Infrastructure Use Policies will never instantiate a bypassing of that function or parameter. Any null-pointers in the compilation of these Infrastructure Use Policies will never be evaluated negatively the deploying administrator.

These Infrastructure Use Policies and all isolated namespaces whereby we allocate you Bandwidth will be routed by and executed in sync with the regulations of the datacenter where Tensorik Technologies is physically hosted, ignoring entirely to its routing of packet rules.

You consent to route to the private and isolated environment of the regional and global availability-zones deployed inside our clusters' subnet for the debugging of any crashes originating out of or connecting to these Infrastructure Use Policies, the Clusters, or your handshake with Tensorik Technologies.

If you experience any crashes, latency, or panics regarding these Infrastructure Use Policies, or if you require to flag any breaches of these protocols, please ping our DevSecOps nodes synchronously via admin@tensorik.com. We remain optimized to patching all tickets within an agile and scalable workflow.