Optimized MySQL, Vertica and Redis data structures and worked across Symfony, Varnish, Nginx and complex deployments supporting 180M+ daily visits.
Maria Carrasco • Software Engineer • CEO
Built by an Engineer Who Has Worked Where Downtime Is Not an Option.
Maria brings enterprise-scale systems thinking to the operational problems that quietly hold growing businesses together.
Engineer first
AI should be operational architecture—not marketing decoration.
Maria Carrasco is a trilingual software engineer and CEO of Technologies IA MDLA Inc. Her work crosses high-traffic web infrastructure, critical networks, aerospace architecture and custom AI business systems.
That background changes the question from “Which AI tool should we buy?” to “Which business function must keep working, what can fail and how will we recover?”
Operating history
Experience shaped by consequence.
Supported network stability and rapid incident response for banking, insurance and federal/postal client environments.
Conceived and implemented an IDG module for PDDS Architecture using MATLAB and advised on software architecture.
Builds AI assistants, custom CRM, CMS, dashboards, admin systems, automation and high-performance digital operations.
The continuity thesis
Growth is fragile when the operation cannot survive interruption.
A company does not become resilient because it bought more software. It becomes resilient when ownership is clear, knowledge is captured, failure is visible and business-critical work has a tested path forward.
- Engineer from business consequence backward
- Remove hidden single points of failure
- Use AI where it increases capacity and continuity
- Keep people in control of judgment and exceptions
- Measure the operational result
Why Technologies IA
Engineering depth for operations where failure has a real cost.
Technologies IA works with established businesses through continuity audits, CRM operating systems, automation sprints, private knowledge infrastructure, and sovereign AI deployments. Every engagement connects technical architecture to ownership, recovery, and measurable business consequence.
Bring an engineer into the business problem before buying another tool.
Start with the failure mode, the exposure and the operating outcome.