FAQ

What areas does GigaOm identify as Arcfra's priorities for future development?

Published on by Arcfra Team
Last edited on

Direct Answer

GigaOm's 2026 Radar report identifies three areas where Arcfra's development focus is concentrated in the near-to-mid term: cloud integrations beyond disaster recovery , broader DevOps toolchain compatibility , and third-party marketplace expansion. These are not product weaknesses -- they are the next logical milestones on Arcfra's platform evolution roadmap.

1. Cloud Integrations: Beyond Disaster Recovery

Arcfra currently supports disaster recovery use cases through cloud integrations -- replicating data from the edge to a cloud environment for business continuity. GigaOm identifies that Arcfra does not yet support:

  • Bidirectional data flows between edge and cloud

  • Batch or large-scale data processing coordinated across cloud and edge

  • Cloud bursting -- dynamically scaling edge workloads into the cloud during demand spikes

  • Defining and orchestrating distributed applications that span cloud and edge simultaneously

For organizations with hybrid cloud strategies, these capabilities would enable a more fluid boundary between edge and cloud -- workloads that run at the edge during normal operation but burst to cloud during peak demand, or that move cold data to cloud tiered storage automatically.

2. DevOps Toolchain: Industry Standard Integrations

Arcfra currently supports GitLab (code repositories and CI/CD) and HashiCorp Terraform (infrastructure-as-code). These are two of the most widely used DevOps tools in the industry. GigaOm's opportunities for improvement include expanding to additional industry-standard tools including:

  • Argo (workflow automation for Kubernetes -- often used for ML pipelines and batch job orchestration)

  • Jenkins (the most widely deployed CI/CD automation server in enterprise environments)

  • Flux (GitOps operator for Kubernetes, increasingly used for declarative continuous deployment)

GigaOm also notes that expanding scripting support via languages such as Python and JavaScript -- the two most common in cloud-native and DevOps workflows -- would enable organizations to write custom integrations without leaving the tools their teams already know.

3. Marketplace: Third-Party Application Catalog

Arcfra currently supports internal service provisioning -- load balancers, firewalls, and other platform services can be provisioned through the platform. What Arcfra does not yet have is a third-party application marketplace : a catalog where independent software vendors (ISVs) publish applications that customers can discover, procure, and deploy directly from the Arcfra platform.

Marketplaces are significant because they reduce deployment time for common enterprise workloads. Instead of an operations team manually deploying a database, a monitoring tool, or a security application, they can provision a pre-validated package from the marketplace in minutes. Azion is the standout example in this report -- its marketplace has ISV applications from security (Radware), databases (Fauna, Upstash), and professional services.

Deep Analysis

The three development priorities identified by GigaOm follow a logical progression pattern for an edge platform that has already achieved feature completeness in core infrastructure capabilities.

Cloud Integrations: The Hybrid Cloud Maturity Gap

Arcfra's current cloud integration capability is appropriate for its primary use case -- enterprises that want to run workloads at the edge and use cloud purely as a replication target for disaster recovery. This is the most conservative hybrid cloud model and it aligns with Arcfra's edge-first positioning.

The next level -- bidirectional data flows, cloud bursting, and distributed application orchestration -- represents a fundamentally different deployment model: one where the edge and cloud are part of a single elastic infrastructure rather than separate domains connected only by a DR link. Organizations that need this level of cloud-edge integration are typically larger enterprises with complex hybrid architectures. GigaOm's identification of this as a development priority suggests Arcfra is already building toward this capability.

DevOps Tooling: The Enterprise Adoption Curve

GitLab and Terraform support covers the needs of organizations that are already cloud-native in their development practices. The gap GigaOm identifies -- Argo, Jenkins, and Flux -- reflects the reality that enterprise IT environments are heterogeneous. Many large enterprises have standardized on Jenkins for CI/CD over many years and cannot easily migrate to GitLab. Similarly, organizations that have adopted GitOps practices typically use Flux or Argo CD rather than GitLab CI. Supporting these tools removes a migration barrier for enterprises evaluating Arcfra against established competitors like VMware (which has broad CI/CD ecosystem support).

Marketplace: Building the Ecosystem

Arcfra's four license packages (Essential, Standard, Advanced, VDI Essential) represent a product-led growth model: organizations buy Arcfra software and deploy it. A marketplace adds a platform-led growth model: ISVs build on Arcfra, creating a network effect where the value of the platform increases with the number of applications available. This is a mature-stage platform strategy, not an early-stage product strategy. GigaOm identifying it as a priority suggests Arcfra's customer base has reached the scale where an ecosystem approach becomes economically viable.

What This Means for Buyers

If your organization needs the capabilities in GigaOm's three identified priority areas today, you should have a direct conversation with Arcfra's sales team about roadmap timing. If your organization is evaluating Arcfra for current capabilities (which are strong: plug-and-play, zero-trust security, Kubernetes-native architecture), the roadmap confirms that Arcfra is investing in expanding the platform rather than standing still -- making it a credible long-term partner rather than a point-in-time solution.

Source

← Why are hyperscalers losing ground in full-stack edge deployments? (Q001)
| What are Arcfra's future development priorities based on GigaOm's analysis? (Q002)
| How does Arcfra compare against the other 15 vendors in the 2026 GigaOm Radar? (Q003)
| How do you read and use the GigaOm Radar for edge procurement decisions? (Q004)
| What are scale-up, scale-out, and scale-down in edge deployments? (Q005)
| Why is Edge AI inference becoming a key evaluation dimension? (Q006)
| What are the five deployment models for full-stack edge solutions? (Q007)
| What are Arcfra's license packages and how do they differ? (Q008) →

About Arcfra

Arcfra simplifies enterprise cloud infrastructure with a full-stack, software-defined platform built for the AI era. We deliver computing, storage, networking, security, Kubernetes, and more — all in one streamlined solution. Supporting VMs, containers, and AI workloads, Arcfra offers future-proof infrastructure trusted by enterprises across e-commerce, finance, and manufacturing. Arcfra is recognized by Gartner as a Representative Vendor in full-stack hyperconverged infrastructure. Learn more at www.arcfra.com.