The warning was in the rehearsal. A global manufacturer was spending tens of thousands on disaster recovery tests, and the tests were failing. Its data center contract was approaching expiry. Its hardware needed replacing. Database support was nearing its end. Management wanted the IT bill reduced. There was less than eight months to build an answer.
- Data Intensity assesses, moves and runs business-critical Oracle systems.
- Licensing, recovery and operating costs shape the cloud decision.
- Its work spans Oracle Cloud, Azure, AWS and hybrid environments.
A recovery plan that would not recover
Data Intensity’s account of that unnamed customer contains a revealing detail: the destination was Microsoft Azure. The manufacturer already ran workloads there, including an Oracle E-Business Suite instance. Azure’s load balancing and recovery services could fit into something the customer already understood. The reported result was a 40% reduction in infrastructure costs and a working recovery solution.
The interesting thing is the sequence. A deadline, a failed test, an inventory of existing systems, then a platform choice. That sequence explains the appeal of Data Intensity, an Oracle specialist whose work reaches from software licensing into the daily running of enterprise applications. The customer buys help making a difficult decision, then help living with it.
The license comes along for the ride
Moving an Oracle application involves more than finding a new home for its database. Data Intensity’s Total Cost of Ownership Transformation Assessment, or TCOT, examines the economics of the estate. Its Cloud Platform Assessment considers usage and alternatives across Azure, AWS and Oracle Cloud Infrastructure, usually shortened to OCI. The starting point is what the customer owns, uses and needs.
That can unsettle a decision already gathering momentum. In its customer video listing, Data Intensity describes Suffolk Construction considering an Azure move before a TCOT assessment revealed another option. The lesson a buyer can copy is straightforward: let the assessment challenge the preferred destination before the migration becomes expensive to reverse.
Execution has its own discipline. The company’s Safe-Switch methodology starts with discovery and assessment, moves through design, then tests cloud services and pilot migrations before final cutover. Ongoing management follows. A useful migration plan therefore has two destinations: the new environment and the team responsible for operating it.
- 01DiscoverInventory + constraints
- 02DesignOptions + architecture
- 03MigratePilot + test + cutover
- 04ManageOperate + optimize
Oracle’s published architecture account makes the mechanics tangible. Data Intensity moved a customer’s E-Business Suite, Hyperion, database and middleware workloads to OCI. Three non-production database servers became two. Oracle reports a 60% labor-cost reduction from the Hyperion migration. Production ran in Ashburn, with disaster recovery in Phoenix. The recovery objectives allowed one hour of potential data loss and 24 hours to restore service. Those limits matter as much as the savings.
An Oracle alumnus, then two buyouts
The company’s Oracle roots are personal. Co-founder Brian Stefano worked at Sybase and then Oracle before helping start Data Intensity. His biography at UMass Lowell describes the enterprise cloud business and its subsequent sales to Audax in 2012 and EQT in 2017. The company dates its founding to 2001.
At the 2017 acquisition, EQT described a business managing more than 3,000 application instances and 10,000 databases. It was already operating internationally, with more than 650 employees. The attraction was the combination of application knowledge, technical operations and delivery across different IT environments. The acquisition announcement did not disclose a purchase price.
Today, Data Intensity’s about page reports 800 professionals and 450 active Oracle certifications. Its careers material describes mentorship, continuing education and certification training. In a services company, those practices have a commercial purpose: the expertise must survive changes in software versions, platforms and customer requirements.
Someone has to run Monday morning
The portfolio includes E-Business Suite, PeopleSoft, JD Edwards, Hyperion and Fusion Cloud Applications. Technical operations sit beside functional application support, the work of helping people use the software. Public customer examples range from Rexel Australia and LiDestri Foods to logistics provider Cory Brothers and semiconductor company Synaptics. These are businesses with substantial systems already in place.
The business model follows that installed base. Assessments, migrations and implementations create project work. Monitoring, patching, support and optimization create recurring service relationships. Data Intensity occupies the space between cloud infrastructure and the people who rely on an application to get work done. Datavail offers overlapping Oracle consulting and managed services; internal teams are another alternative. Buyers should compare the scope of responsibility alongside the platform expertise.
“Migrating to the cloud is a journey, and ‘going live’ is not the end of that road.”James White, Chief Solutions Officer / February 2025
That observation explains the 2025 expansion of its Matilda Cloud partnership. Data Intensity had used an internally developed Cloud Care tool; Matilda Optimize promised faster analysis and deeper visibility. The operational concern was cloud sprawl: resources and spending that require continued scrutiny after launch. A migration can succeed while its economics gradually deteriorate.
The price of handing over the pager
The newer managed GitLab offering makes the tradeoffs unusually visible. Launched in February 2026, DevSecOps as a Service runs a dedicated GitLab environment on OCI with monitoring, patching, backups and recovery. Customers can align updates with their own change windows.
GitLab licensing, migration and specified additions are priced separately.
The Standard tier lists a 48-hour recovery time objective and a 24-hour recovery point objective. Premier+ lists four hours and 15 minutes respectively. Buyers needing faster recovery must assess those limits carefully. A small team comfortable running its own tools may find little reason to buy this service. An enterprise with licensing complexity, aging applications and scarce operating expertise has a different calculation. Start with the inventory. Put recovery requirements beside the price. Then choose who gets the pager.