Compute Allocation & Consumption#

Edilitics relies on compute resources to execute data replication and transformation workflows. Each subscription plan provides a specific compute allocation, with the flexibility to purchase additional resources as needed.

This guide explains how compute is allocated, consumed, and managed within Edilitics to ensure efficient workflow execution and resource optimization.

Compute Allocation by Subscription Plan#

Free Plan#

• Compute Allocation: 30 minutes per workspace per month (or 30 minutes per month for solo users).

• Reset Schedule: Compute minutes reset at the start of each billing cycle.

• Additional Compute: Not available—users must upgrade to a paid plan for increased compute capacity.

Solo Plans#

• Compute Allocation: 120 minutes per month, suitable for individual analysts and small-scale workloads.

• Reset Schedule: Compute minutes reset monthly based on the subscription renewal date.

• Additional Compute: Available for purchase, providing flexibility in scaling resource consumption.

Enterprise Plans#

• Compute Allocation: 120 minutes per user per month, aggregated at the workspace level (e.g., 10 users = 1200 minutes/month).

• Reset Schedule: Compute minutes reset monthly, aligning with the organization’s subscription cycle.

• Compute Usage Management:

  • Centrally managed at the workspace level, allowing adaptive resource allocation across users and workloads.

  • Optimized for high-volume processing, ensuring equitable distribution of resources within teams.

• Additional Compute: On-demand compute scaling is available to accommodate intensive workflows.

Additional Compute Pricing#

Users requiring additional compute resources can purchase extra minutes at the following rates:

✅ Purchased compute minutes do not expire, ensuring resource flexibility for scaling mission-critical operations.

Compute Consumption in Edilitics#

Compute minutes are deducted based on actual execution time for replication and transformation workflows.

Deployment & Initialization (Setup Phase)

• Dynamic Compute Provisioning

  • A dedicated compute instance is instantiated in real time when a workflow is triggered.

  • Setup time is included in compute consumption, covering VM provisioning, secure credential handling, and workflow initialization.

• Security & Credential Management

  • Encrypted credentials are transferred securely to the VM.

  • Credentials do not persist beyond execution.

Execution & Processing (Compute Deduction Phase)

• The system extracts data from the source, applies necessary processing logic, and loads it into the destination system.

• Compute minutes are deducted based on:

  • Time spent extracting data from the source.

  • Time taken to process the data (Replication: formatting, schema validation; Transformation: filtering, restructuring, aggregations).

  • Time spent loading data into the destination.

Teardown & Cleanup (Completion Phase)

• Compute Instance Deallocation

  • The compute instance is securely terminated once execution is complete.

  • Total runtime—including teardown—is deducted as consumed compute.

How Compute is Managed in Edilitics#

Allocated vs. Purchased Compute

• Allocated Compute

  • Resets monthly based on the subscription cycle.

  • Unused minutes do not roll over, requiring users to utilize the allocated quota within the month.

• Purchased Compute

  • Does not expire, allowing scalability for high-demand workloads.

  • Can be used only after allocated compute is fully consumed.

Handling Compute Exhaustion#

✔ Automatic 15-Minute Buffer

• If compute is depleted mid-execution, Edilitics grants up to 15 additional minutes to complete the workflow.

✔ Negative Balance Handling

• Workflows can continue up to -15 minutes in negative balance before stopping.

✔ Adjustments for Next Month

• Any overage is deducted from the next month’s allocation.

• Users must purchase additional compute or wait for quota replenishment to resume execution.

✔ Workflow Pausing

• If compute reaches zero or a negative balance beyond -15 minutes, all active workflows are paused.

• Workflows must be manually resumed once new compute is allocated or purchased.

Tracking Compute Consumption#

Users can track real-time compute usage to ensure efficient execution and avoid unexpected depletion.

Where to Track Compute Usage?

• Usage Summary Dashboard (Under Org Settings)

  • Shows total compute allocated, used, and remaining.

  • Displays compute breakdown by user and workflow type.

• Workflow Execution Logs

  • Shows compute consumption per execution, allowing users to identify high-usage workflows.

Understanding Compute Allocation & Consumption#

Edilitics' compute allocation and consumption model ensures predictable resource usage, transparent scaling, and uninterrupted workflow execution.

✔ Monitor consumption trends – Track compute usage in real time to anticipate when additional resources may be required.

✔ Identify high-consumption workflows – Analyze workflow execution logs to detect flows consuming excessive compute and optimize them if possible.

✔ Prevent workflow failures – Purchase additional compute before depletion to avoid operational disruptions.

By tracking usage patterns, proactively managing compute purchases, and optimizing high-consumption workflows, users can ensure reliable data processing and avoid workflow interruptions. 🚀