Granica Platform FAQ
Get answers to common questions.
What is Granica?
The Granica AI Data Readiness platform (or just "Granica" for short) is a suite of services to help data hungry organizations build and manage high quality data for AI, at scale. Our platform uses AI to continuously improve data, making analytical, ML and AI projects faster and more effective over time. Simply put, Granica increases the safety, efficiency, and effectiveness of AI. For more check out the Granica overview.
Does my data leave my environment?
No it does not. Granica uses a self-managed, cloud-prem (i.e. private) deployment model in your public cloud environment, and only control plane data and telemetry metrics are shared with Granica corporate systems and employees.
What is the Granica deployment model?
Granica is deployed as managed software that runs in your AWS or GCP cloud account. Granica consists of a control and data plane that is lightweight; is deployed together with the first Granica product you choose to use; and provides shared infrastructure and services to all subsequently deployed Granica products. This platform/product packaging simplifies and streamlines the architecture, making it easy for you to quickly and cost-effectively enable additional Granica products as your needs dictate. For more see the Granica architecture.
How do I integrate Granica into my environment?
Granica typically processes your data in the background, reading from and writing to cloud storage without requiring any application integration whatsoever. Some services, such as Granica Screen real-time data safety, provide an API/SDK to integrate with your applications (for example LLM-enabled applications). For more see how Granica Crunch works.
How do you ensure my deployment is a success?
Your Granica instance generates usage, system health and performance telemetry data which is automatically shared with Granica engineering and support teams to enable predictive analysis, alerting, troubleshooting, and overall success. Telemetry data is preserved in a cloud storage bucket unique to each customer and deployment, entirely separate from customer data. A subset of this telemetry data is also available for you to view at any time via both the CLI and a graphical dashboard. No customer data is ever collected or analyzed.
How do I "undo" a Granica deployment?
At any time you can simply uncrunch your any data already ingested and reduced by Granica Crunch to return it to its original unreduced form, and then teardown your deployment to return your environment to its pre-Granica state.
How do you ensure your API services are highly available?
Granica provides HA via the native capabilities of kubernetes clusters in AWS (via EKS) and Google (via GKE), configured to use multiple availability zones. Both EKS and GKE provide an SLA of 99.95% availability. For additional detail see High Availability.
How do you achieve exabyte-level scale?
Granica automatically scales out additional nodes (beyond the 2-node minimum for HA) to dynamically handle arbitrarily large data volumes for background services such as Crunch and Screen, as well as real-time API services such as Screen LLM safety guardrails. Scaling is also completely elastic, so as load decreases Granica automatically shuts down unneeded nodes. This minimizes operational costs and maximizes your savings from Crunch. For additional detail see Elastic Scaling.