Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Status and availability

On this page (8)

Where the platform runs, what we commit to by contract, where to follow availability and which features are still being certified.

Where the platform runs#

  • Infrastructure: hyperscale cloud, São Paulo region. Each workspace's datalake (landing, Bronze, Silver and Gold) and the load processing stay in Brazil.
  • Your data under your control: each workspace has its own datalake, isolated from the others. In the own cloud model (included from Scale, add-on on Business), the datalake runs in your company's cloud project — the data stays in your account.

Availability and SLA#

PlanMonthly availability
Starterbest effort, no percentage
Growth, Business and Scale99.5%
Enterprise99.5% or the contract percentage, whichever is higher
  • Service credit: a month below 99.5% gives 10% of the monthly fee; below 99.0%, 25%. The credit is capped at 25% of the monthly fee and is deducted from the next invoice. Full rules in Service level (SLA).
  • Public measurement: the availability of each of the last 90 days is at /status. It is the same series used to calculate the credit.
  • Your own monitor: GET /api/health is public and returns 200 when the application and the metadata database respond, or 503 when a required dependency is down.
  • Internal engineering targets: 99.9% application availability, 99.0% pipeline run success and dashboard queries under 8 seconds at p95. The contractual commitment is the one in the table above.

Support#

  • Aiô — 24 hours, 7 days, inside the system (button on every screen or ⌘/). It investigates your workspace's runs, logs, tables and dashboards and proposes the fix, which you confirm.
  • Human support — 9 a.m. to 6 p.m., Monday to Friday (Brasília time), at suporte@ingestia.io or on the Support screen. First response: Starter 1 business day · Growth 8 business hours · Business 4 business hours · Scale 2 business hours · Enterprise per contract.

Details in Support Center.

Integration surfaces#

SurfaceStateNotes
API key authenticationavailableworkspace-level scope; only the owner creates/revokes
OData v4 (feed)availableOData subset; see limits below
Power BI / Excel kitavailablefolding + incremental refresh
Embed SDK (embedded dashboard)availableglobal origin allowlist today
REST query API (/api/v1/query, /api/v1/tables)early accessnot yet open for external use; use OData
Webhook subscription (events → your endpoint)planneduse polling/OData
Write API (INSERT/UPDATE/…)plannedthe platform is read-only today
Per-member API key (with row-level security)plannedtoday the key is workspace-level

Features being certified#

Connectors

The catalog grew through a declarative engine: ERPs, stores, payment providers, CRMs, marketing platforms, productivity tools, Brazilian public data, warehouses queried over HTTP, remote folders and buckets, and compatible databases (MariaDB, Redshift, CockroachDB, Supabase, Neon, TimescaleDB, AlloyDB, Azure SQL). The full list, with each one's state, is in Connectors.

  • A new connector starts in Limited access: the first run with a real credential is followed by our team before the full release, one connector at a time.
  • Planned (configuration is refused with the reason): TOTVS Protheus, Senior and PagBank — the API is not public/stable or does not list records. NetSuite remains refused until the subscription is verified.
  • S3 and Google Cloud Storage as a source are in Limited access (remote files adapter), under the same rule.
  • API extraction is full on every run (no incremental window from the scheduler yet) and runs within the function time limit — very large sources may need to be split by resource.

Known limitations#

Data and pipelines

  • Leading zero: a digits-only identifier (CPF without punctuation, ZIP code, code 00123) is read as a number in Bronze and loses the leading zero — this applies to CSV and to databases. Send the field formatted. See Import a file.
  • Personal data (PII): it is found by name and by value and flagged automatically on each load; the flag applies to the column name across the whole workspace (the same name in another table is also masked). See Governance.
  • Partial run (one task failed) is not retried and does not go to the DLQ; leaving the DLQ is done through support. See Scheduling, retry and DLQ.
  • Recovering deleted data: 7 days of time travel, through the SQL console — no restore button. See Recover data.

BI, Agents and Aiô

  • Dashboard subscription: Excel, PowerPoint and PDF attachments; the PDF requires the dashboard published with a share link — without it, the email says so and goes with the other two.
  • Agents: do not export data to files; they talk to other systems only via MCP.
  • Aiô: does not create connections or pipelines; the Silver it creates only copies columns.
  • Dashboard template (.json): page names may not be applied (create the pages with + Page and the visuals appear); slicers do not come through the template; applying dozens of visuals takes a few minutes with the screen open.

Scope and credentials

  • The API key reads all published marts in the workspace; there is no per-member/group restriction on this channel. PII columns never leave through the API.
  • Only the owner creates/revokes keys.

OData / Power BI / Excel

  • OData subset: no $expand, $apply, $search, $compute, lambdas (any/all) or arithmetic in filters; text only contains/startswith/endswith. Outside the subset = explicit 501. $format: JSON only.
  • STRUCT/RECORD columns are not published; arrays arrive as a JSON string — avoid repeated columns in marts.
  • Pagination: pages of up to 1,000 rows; maximum depth of 1,000,000 rows/query (above → 400, filter).
  • DATETIME is treated as UTC (the datalake does not store a time zone).

Embed

  • The origin allowlist is instance-wide (per workspace is planned).
  • A non-empty aplicarFiltros reloads the iframe; cross-filter events are not emitted yet.

Cost and limits

  • BRL values (x-ingestia-cost-brl) are an estimate for the query; the amount charged is the one on the invoice.
  • Rate limit: read 120/min per key (240/min per workspace); free SQL 60/min per key (120/min per workspace).

Security#

  • No sensitive information (secrets, customer data, internal infrastructure details) is published here. Security reports: see Support (treat a suspected leak as Critical).

Troubleshooting#

SymptomCauseWhat to do
"The doc says X but the app does Y"possible state mismatchopen a ticket citing the page and the URL
Feature listed as planned or early accessnot yet open for general usefollow the What's new page; talk to support if you need it
System downpossible incidentcheck /status and talk to Aiô or suporte@ingestia.io

Next steps: Support Center · Developers · Troubleshooting.

Related links