Islo Raises $15 Million to Turn AI Coding Into Factory Lines
Islo raised $15 million led by Insight Partners to scale AI software factories with microVM environments, credential gateways, and a Databricks inference partnership.
By Nathan Brooks
4 min read

What's News
- Islo secured a $15 million investment led by Insight Partners to expand its Enterprise Software Factory platform.
- The company announced a Databricks partnership for model inference and enterprise data access, plus inclusion in Databricks' Built on Program.
- Islo Machines use microVMs with their own OS kernels and support snapshots so agent jobs persist across sessions.
- A gateway supplies scoped credentials to agents, who never hold reusable API keys.
- Islo is part of Incredibuild, which acquired engineering-agent firm Kypso in 2025.
Islo has secured a $15 million investment led by Insight Partners to expand its Enterprise Software Factory platform — a bet that the real bottleneck in AI-assisted development is everything that happens after an agent starts writing code. The company, part of the Incredibuild family of products, will spend the money on product development and adoption of the platform as a dedicated product line.
The announcement also includes a partnership with Databricks covering model inference and connections between agent workflows and enterprise data. The two moves target one practical problem: producing more code is useful only if teams can reliably test, secure, review, and deliver it.
What does this change for engineering teams?
Islo describes its approach as a software factory. Instead of a developer initiating every task in a chat window, teams define workflows that respond to events or run on a schedule. The company says early customers are applying this to refactoring, code review, quality assurance, bug fixes, issue triage, and smaller feature requests.
Each workflow carries gates for testing, functionality, security, performance, and cost. Engineering teams decide where human approval is required, and sign-off is retained before AI-generated changes reach production.
"AI can dramatically increase the amount of code an engineering organization produces, but that doesn't automatically translate into more software being delivered safely," said Adam Gold, Islo's chief product officer, in the announcement.
That distinction changes what an agent platform must provide. Generating a patch is one step; running the application, checking the patch against its dependencies, and showing a reviewer what happened are separate engineering tasks.
Why persistent environments matter
The foundation is Islo Machines — isolated development environments that can run an application's services alongside an agent. The company describes these as microVMs: lightweight virtual machines with their own operating-system kernels, rather than containers sharing the host kernel.
A Machine can include dependencies, configuration, a browser, databases such as Postgres, and services such as Redis. That gives an agent a working application to exercise instead of asking it to reason about source files alone.
Persistence addresses another limitation of short-lived sandboxes. Snapshots preserve installed dependencies and database state, so subsequent work resumes from a prepared environment. Jobs can continue after a developer disconnects — important for tasks that take hours or span multiple iterations.
Islo also offers deployment inside a customer's virtual private cloud. For enterprises, that makes the location of the runtime part of the deployment decision alongside the choice of model and agent tooling.
A gateway that separates agents from secrets
An isolated computer still needs controlled access to repositories, issue trackers, and other systems. Islo's gateway checks outbound requests and supplies credentials only when an approved request leaves the environment.
In the company's workflow, an agent uses a placeholder binding rather than receiving the underlying secret. Gateway rules can restrict destinations, URL paths, and request methods, and an optional model-based judge can assess request intent alongside those static rules.
This separates permission to perform a task from possession of a reusable API key. An agent reviewing a pull request can receive access appropriate to that workflow without being handed the same broad credentials a developer holds.
Allowed and denied requests are logged, with export to security monitoring systems. Teams can reconstruct which external services an agent contacted and which operations its policies blocked. The effectiveness of that boundary still depends on the permissions and rules each enterprise configures.
Databricks, inference, and the data layer
The Databricks relationship adds inference — running a model to generate a response — and access to the enterprise data agent-driven work requires. Islo's integration page describes connecting an existing workspace through brokered credentials. Agents can use models available through Databricks Model Serving and request scoped access to the customer's compute and data.
Data processing stays on the customer's Databricks clusters, while Islo supplies the isolated agent environment and controlled connection. The integration records requests and jobs for review, supporting workflows such as data engineering, analysis, and batch processing.
The release describes inference as the starting point for a broader product integration and confirms Islo's inclusion in Databricks' Built on Program. That connects the software-factory strategy to an existing enterprise data platform, rather than requiring teams to duplicate their data in a separate agent tool.
Built on Incredibuild's delivery infrastructure
Incredibuild contributes distributed execution and caching technology. Distributed execution spreads suitable build or test work across compute resources; caching reuses previous outputs when relevant inputs haven't changed. Both shorten the feedback cycle between an agent proposing a change and a team learning whether it works.
The relationship follows Incredibuild's acquisition of Kypso in 2025. Kypso's engineering agents and workflow automation drove Incredibuild's expansion beyond build acceleration into a broader software delivery platform.
For Islo, the $15 million backs the infrastructure around autonomous engineering: environments that stay available, permissions that can be enforced, and checks that connect generated code to release decisions. Its opportunity is making repeated development work dependable enough to delegate — while keeping engineers responsible for what ultimately ships.
Source: unite.ai
More from Nathan Brooks
Show full bio
News editor covering regulation, policy and their impact on entrepreneurship, startups and venture funding at Business Bearings.
2,276 articles