Bare metal can be very cost-efficient. The tradeoff is owning the software, resilience, upgrades, deployment pipeline, and every operational handoff around it.
Identity, data, files, events, and business workflows are available when your Arc deployment is provisioned. Give your team and AI agents more room to build the product, connect enterprise systems, and create customer value.
Connected identity, permissions, data, sync, and business APIs. Capacity and integration scope agreed for your workload.
Infrastructure + selected services
USD / month · Estimated service budgets, before tax
See what changes when you host it yourself or add another provider.
Add your monthly quote for services such as search, email delivery, or audit exports. Baseline monitoring is already included above.
Identity, users, permissions, data, sync, and business workflows share one API foundation and managed deployment.
| What you need | DIY components | Estimated monthly cost |
|---|---|---|
| Estimated monthly DIY total | ||
Approximate budgets for a roughly comparable service stack. Capacity, region, traffic, and architecture affect the final bill. Initial API development and integration, payment processing, and AI model usage are additional.
A production cluster from Tier 1. The base scope includes application compute, a resilient database cluster with recovery capacity, streaming and queues, load balancing, DNS, security controls, monitoring, backups, object storage, and CDN delivery in one region. Tier 2 increases compute, data, and traffic headroom. Tier 3 adds a larger footprint and a second-region budget allowance.
Bare metal budgets multi-node server capacity for APIs, replicated SQL, and Kafka together. The database and messaging rows share that server capacity and are not charged a second time. Network, backup, and delivery costs are separate. Linked server prices may use a different currency; these USD ranges are independent estimates.
These tiers compare similar service responsibilities; they are not Arc hardware specifications or throughput commitments. Costs use a 730-hour month and on-demand-style capacity budgets. Usage, recovery targets, cross-region replication, and discounts change the result. Leased dedicated servers; location and provider vary.
Open source still needs runtime. The Keycloak selection adds dedicated application-node capacity; its database, routing, and baseline monitoring use the infrastructure already budgeted. No Keycloak license or per-connection fee is added. Maintenance is optional below the service choices. WorkOS uses its free basic user-management tier up to 1M monthly active users; SSO and directory sync add separate connection fees only when selected. Another provider uses the fee you enter. Only one identity-provider option is counted.
The application layer matters, too. A cloud account and an identity service still need to be connected to your product’s permissions, data model, content, subscriptions, agreements, invoices, and transaction workflows. Building and integrating that API layer is outside this monthly services estimate. Arc Fusion supplies the connected API suite with its managed deployment; confirm required integrations and scope with our team.
Category ranges are Arc estimates informed by the linked vendor pricing and architecture references, rather than vendor quotes. Sync-worker ranges are additional runtime budgets; they do not include initial connector development.
| Responsibility | Arc Fusion | DIY path |
|---|---|---|
| Application service APIs | Connected suite included | Build or integrate each capability |
| Deployment isolation | Customer-isolated deployment | Design and enforce the boundaries |
| Compute, data, storage & messaging | Configured as a managed foundation | Provision, connect, secure, and operate |
| Capacity and regions | Resize or expand the agreed deployment | Plan topology, changes, and validation |
| Service replacement | Integrate and replace through planned boundaries | Own all integrations and migration work |
Arc Fusion brings the services together so your team can focus on the product. You can integrate external providers and replace components as your requirements change.
Use your existing identity, data, or application services where they make sense.
Put integration boundaries around the capabilities you may want to replace later.
APIs and data mappings help scope a migration. Move components in stages, with integration work and validation planned for each provider.
Compare the service stack and estimated monthly costs by tier.
Explore comparisonARC FUSION vsCompare the service stack and estimated monthly costs by tier.
Explore comparisonARC FUSION vsCompare the service stack and estimated monthly costs by tier.
Explore comparisonARC FUSION vsCompare the service stack and estimated monthly costs by tier.
Explore comparisonFrom the first user to the whole business workflow.
Let’s build it with Arc Fusion.