Configure Crunch
System-wide platform settings that control how Granica Crunch operates, calculates savings, and communicates with your team.
Platform Configuration contains the system-wide knobs that govern how Granica Crunch operates across your entire deployment. Changes take effect immediately for all users. Only users with the Admin role can modify these settings.
Navigate to Settings → Platform Configuration to access this page.
Platform
General identity and catalog sync settings.
| Setting | Default | Description |
|---|---|---|
| Company Name | — | Your organization's name. Appears in report headers and PDF exports. |
| Min Eligible Table Size (GB) | — | Tables smaller than this threshold are excluded when Granica syncs tables from a connected catalog. Raising this value focuses Crunch on high-impact tables and reduces noise from small datasets. |
| Quarterly Goal (PB) | 0 | Target volume of crunched data for the current quarter, used in reporting dashboards. Set to 0 to hide the goal metric from reports. |
Savings & Cost
Parameters used to compute and project the storage savings Crunch delivers. Granica uses these values in the Cloud Savings report and all dollar-denominated savings estimates.
| Setting | Default | Range | Description |
|---|---|---|---|
| Storage Cost ($/GB/month) | 0.021 | 0.001–1 | Your base storage rate before any negotiated discount. The default matches AWS S3 Standard pricing. Adjust for GCP, Azure, or custom rates. |
| Cloud Discount (%) | 0 | 0–90 | Your negotiated cloud discount (e.g. AWS EDP, GCP CUDs). Applied on top of the base rate. The effective rate shown on the page is base_rate × (1 − discount%). |
| Projection Period (months) | — | 1–60 | How many months forward the Cloud Savings report projects future savings based on the current compression ratio. |
| Operational Cost ($/PB) | — | 0–100,000 | Heuristic Crunch operational cost per petabyte of processed data. Used in net savings calculations until direct cloud billing integration (AWS CUR / GCP Billing) is available. |
Crunch Intelligence
Scheduler routing thresholds that determine how Granica distributes and routes crunch jobs.
| Setting | Default | Range | Description |
|---|---|---|---|
| Hourly Fanout Min Partition Size (GB) | — | 10–1,000 | When the average daily partition for a table exceeds this size, Granica splits the crunch workload into 24 per-hour jobs instead of a single daily job. This improves parallelism and throughput for large, frequently updated tables. Tables below this threshold use a single daily job. |
| Mutation Interval Threshold (minutes) | — | 5–120 | The minimum quiet period between data writes required for Granica to route a table to a full crunch job rather than a lighter optimize pass. Lowering this value makes Crunch more aggressive — it will crunch tables even if they have been recently written to. Raising it reserves full crunch runs for tables with longer write-free windows. |
Security and Authentication
JWT token lifetime controls. Changes propagate to newly issued tokens within 60 seconds. Refresh token TTL must always exceed the access token TTL or users will be unable to silently renew their sessions.
| Setting | Default | Range | Description |
|---|---|---|---|
| Console Public URL | (request origin) | — | The public URL at which users reach this Console (e.g. https://console.example.com). Pins all absolute URLs the Console emits, including the SAML SP entity ID, ACS URL, SAML metadata endpoint, OIDC post-logout return URL, and proxy redirects. Set this when the CONSOLE_PUBLIC_URL environment variable is not configured, or to ensure a stable URL across multiple ingresses or DNS changes. |
| Access Token TTL (seconds) | 3,600 | 900–28,800 | How long a user's access token stays valid before it must be refreshed. Shorter values limit the exposure window if a token is compromised; longer values reduce the frequency of silent refresh calls. Default is 1 hour (3,600s). |
| Refresh Token TTL — SSO users (seconds) | 7,200 | 3,600–28,800 | How long an SSO user's refresh token stays valid. When it expires, the user silently re-authenticates through their identity provider. Aligned with typical IdP idle session lengths. Default is 2 hours (7,200s). |
| Refresh Token TTL — local users (seconds) | 604,800 | 3,600–2,592,000 | How long a local (password) or break-glass user's refresh token stays valid. The default is intentionally longer than SSO because local users must type a password on each re-authentication. Default is 7 days (604,800s). |
Email Reports
Controls the theme and recipient list for Granica's scheduled email reports. This section appears only when email reporting is enabled for your deployment.
| Setting | Description |
|---|---|
| Email Theme | Visual theme for email reports: Dark (matches the Granica Console brand) or Light. |
| Daily Report Recipients | Email addresses that receive the daily Platform Status report. Leave empty to send to all users with the Editor or Admin role. |
| Weekly Report Recipients | Email addresses that receive the weekly Data Management report. Leave empty to send to all users with any role (Viewer, Editor, or Admin). |
Saving changes
Edit any field and click Save Changes in the top-right corner or at the bottom of the page. You can edit multiple settings across sections before saving — all pending changes are applied in a single save. Click Reset to discard unsaved edits and revert to the current saved values.
Fields marked Customized have been changed from their factory default. The page shows who last updated each setting and when, along with the original default value for reference.
Monitoring Platform
Overview of the dashboards and reports available in the Granica Console for tracking optimization activity, platform health, and cost savings.
Use Platform Tools
Access the Granica API explorer, Grafana dashboards, Airflow DAG scheduler, and Spark History Server directly from the Granica Console.