TL;DR
The shift, in one breath
Voiply concluded that managing infrastructure internally was not creating differentiation, was not winning customers, and was not accelerating innovation. The company moved to a hosted Oracle Cloud Infrastructure (OCI) environment operated by Crexendo. The NetSapiens platform runs on top. The operating model changed accordingly.
- Internal infrastructure ownership has an opportunity cost. Voiply’s engineers were spending cycles on platform operations rather than customer acquisition, automation, AI, or product.
- Hosted OCI from Crexendo removed the operational burden. High availability, failover, resiliency, scaling, maintenance, and platform operations are handled by Crexendo.
- Failover is invisible to end users. Voiply confirmed seamless rollover with no dropped calls when an environment went down.
- The operating model shifted. Voiply reallocates engineering toward customer acquisition, automation, AI, software development, and market expansion.
- The deeper choice was strategic identity. Voiply chose to be a sales and marketing company, not an infrastructure company.
Table of Contents
Every UCaaS service provider eventually reaches the same fork in the road. Do you run the platform infrastructure yourself, or do you let someone whose entire business is running that infrastructure do it for you? Most operators, at some point, have run it themselves. They built data center relationships, hired site reliability engineers, mapped out failover regions, wrote runbooks for hardware refreshes. The work was real and the work mattered. It just did not differentiate the business.
Voiply, a fast-growing UCaaS service provider supporting more than 40,000 subscribers, reached that fork and made a definitive call. Voiply chose to run the NetSapiens platform on Crexendo’s hosted Oracle Cloud Infrastructure (OCI) environment rather than continue to operate the underlying platform infrastructure internally. The decision was not driven by cost optimization or by infrastructure complexity that had become unmanageable. It was driven by a clear-eyed read of where engineering effort actually creates competitive advantage in 2026 — and where it does not.
What managing infrastructure was actually costing VoIPly
Voiply’s evaluation identified the real cost of self-managed infrastructure, which is not the line items most operators model. The real cost is the engineering attention that platform operations consume — attention that cannot then be applied to anything else. High availability work. Failover testing. Resiliency planning. Capacity scaling. Maintenance windows. Patch cycles. Every hour spent on those activities is an hour not spent on automation, AI integration, customer acquisition tooling, or anything an end customer can see or value.
None of that work was creating differentiation for Voiply. None of it was winning new customers. And critically, none of it was accelerating the rate at which Voiply could ship product. For a company on the growth trajectory Voiply is on, that pattern is structurally unsustainable. Engineering hours are the scarcest resource a service provider has. Pointing them at infrastructure maintenance is pointing them at a problem that does not pay back at the margin.
What Crexendo's hosted Oracle Cloud Infrastructure environment removes from the equation
By moving the NetSapiens platform to a hosted OCI environment operated by Crexendo, Voiply eliminated the operational burden of maintaining the platform and underlying infrastructure internally. High availability, failover, resiliency, scaling, maintenance, and platform operations all moved to Crexendo. Crexendo runs the environment. Crexendo owns the SLA. Crexendo absorbs the operational surface area that previously belonged to Voiply’s internal team.
What that actually feels like in production matters more than what it looks like in a vendor diagram. When an environment goes down — and at carrier-grade scale, environments occasionally go down — the operator’s end customers should not be able to tell. Voiply’s experience on Crexendo’s hosted OCI confirmed that.
"If one environment went down, everything rolled over seamlessly, no dropped calls."
— Shea Georgetti, Co-Founder & CEO, Voiply
That is the bar carrier-grade hosting has to clear. Seamless rollover. No dropped calls. Not a status-page notice after the fact, not a one-hour recovery window. Genuinely invisible to the end customer, which means genuinely invisible to Voiply’s brand. Crexendo’s hosted OCI clears that bar because clearing it is the entire point of the offering.
What VoIPly could do once infrastructure stopped owning its engineering team
The financial accounting of a hosting decision is straightforward, and many operators stop their analysis there. The operating-model accounting is more consequential. When Voiply stopped managing infrastructure, Voiply changed what kind of company it could be.
Instead of building an organization around platform operations, Voiply could invest more heavily in the activities that actually grow the business. Customer acquisition. Automation that compounds across every new tenant. AI integration that turns platform data into operational advantage. Software development on top of the NetSapiens API surface. Market expansion into geographies and verticals that were previously not even on the roadmap because the engineering bandwidth was committed elsewhere.
SUBSCRIBERS SUPPORTED
CONCURRENT-SESSION SCALE (50 → 600
DROPPED CALLS DURING FAILOVER
Shea Georgetti, Voiply’s Co-Founder and CEO, framed the deeper logic in a single line:
"We want to be a sales and marketing company, not an infrastructure company."
— Shea Georgetti, Co-Founder & CEO, Voiply
That sentence is not a slogan. It is a strategic identity claim that has implications across every hiring decision, every quarterly plan, every product investment. A service provider that has chosen to be a sales and marketing company allocates engineering toward customer-facing work. A service provider that is still functionally an infrastructure company cannot, because its engineering attention is committed to keeping the platform running.
What this means for service providers facing the same decision
Every UCaaS operator currently running platform infrastructure internally should be asking the same questions Voiply asked. Is internal infrastructure management creating differentiation? Is it winning customers? Is it accelerating innovation? If the answer to any of those questions is no — and for most operators on most days, the answer is no — then internal infrastructure ownership is consuming engineering attention that would compound better somewhere else.
Running the NetSapiens platform on Crexendo’s hosted OCI environment is not a procurement decision. It is a decision about what kind of service provider an operator wants to become over the next decade. Voiply made that decision deliberately, with the evaluation work to support it, and the operating-model outcome speaks for itself. The question for every other operator is whether they have looked at the same fork in the road, and what they have decided.
See what running the NetSapiens platform on Crexendo's hosted OCI looks like for an operator your size.
Crexendo delivers the NetSapiens platform on hosted Oracle Cloud Infrastructure, in the operator’s own cloud, or in hybrid configurations. Bring your scale, growth trajectory, and AI roadmap.
