Navera Engine

1. What cloud providers do you support?

We currently support Google Cloud Platform (GCP) only. AWS and Azure support are coming soon.

​​

2. What services can I use in a pipeline?

You can choose from cloud-native data and AI services like Cloud Storage, Dataflow, BigQuery, Vertex AI, Cloud Functions, and more — depending on your tier.

​​

3. How are “services” counted in my plan?

Services are counted based on the number of cloud services you use per organization. These are shared across all your projects and team members.
For example, a pipeline with Cloud Storage → Dataflow → BigQuery counts as 3 services.

​

4. What happens when I hit my service cap?

You can either remove unused services or upgrade your plan. On Pro and Business tiers, you can add more services for $19/month per 10 services.

​​

5. Can I modify my pipeline after deploying it?

Yes. You can change, redeploy, or version your pipeline at any time. Navera tracks changes and ensures reproducibility.

​​

6. Do I need to know Terraform or YAML to use Navera?

No. Navera handles all infrastructure-as-code for you. You define your pipeline — we generate and manage the Terraform and YAML behind the scenes.

​

7. Does Navera deploy the actual infrastructure in my cloud account?

Yes. Navera uses your credentials to deploy infrastructure directly into your own cloud account — securely and with best practices.

​​

8. Is my infrastructure portable if I stop using Navera?

Yes. Navera generates Terraform-based infrastructure, so you can export configurations and continue managing them independently if needed.

​

9. Can I collaborate with my team?

Team collaboration is available on the Business and Enterprise tiers. You can manage users, assign roles, and track shared usage.

​

10. What’s the difference between an organization, a project, and a pipeline?

An organization is the top-level workspace that brings together your users, projects, and service usage under one account. It lets you manage billing, track usage, and control access across your entire team.
A project represents a single cohesive use case (e.g., data ingestion, AI training). Each project can include one or more pipelines — sequences of connected services like Dataflow → BigQuery → Vertex AI.
A pipeline is a sequence of connected cloud services within a project — such as Dataflow → BigQuery → Vertex AI — that execute a specific task or workflow.

​

11. What’s the difference between Pipeline Template use, custom Pipeline Template saves, and the collaborative Pipeline Template library?

Pipeline Template use means you can access and deploy any of Navera’s pre-built pipeline templates as much as you want. This is unlimited across all plans.

Custom Pipeline Template saves let you save your own pipelines as reusable templates. In Free and Pro plans, this works as a personal versioning/rollback tool so you don’t lose work when experimenting.

Collaborative Pipeline Template library is included in Business and Enterprise plans and allows your team to share custom pipeline templates with each other, standardize best practices, and build a shared catalog across projects.

​

12. What are Pipeline Cost Guardrails?

Pipeline Cost Guardrails are automated cost controls built into Navera. They let you:

• Get cost estimates for your pipeline before you deploy it

• Set automated actions if costs exceed thresholds (e.g., stop the pipeline, alert you, or block deployment)
  This ensures you stay within budget and avoid unexpected bills.

​

13. What does “x pipelines/day · y hours each” mean in the Sandbox feature?

Each tier includes access to a sandbox environment — a safe space to run pipelines without connecting your own GCP account.
“x pipelines/day” is the number of test runs you can execute per day, and “y hours each” is the maximum runtime for each pipeline. For example, “2 pipelines/day · 1 hour each” means you can run 2 separate pipelines per day, each lasting up to 1 hour in the sandbox.