Nonprofit and For-Profit: Why We Chose Both

By Anushka Appala and Dr. Janio Rosales

One of the first questions anyone asks about NaciluzIA is also one of the fairest: is this a company or a charity? People want to know who owns it, who profits, and whether the "open standard" language is real or a marketing coat of paint over an ordinary vendor. It is a reasonable suspicion, because the history of government technology is full of open-sounding promises that quietly hardened into lock-in.

Our answer is that NaciluzIA is deliberately both — a nonprofit foundation and a for-profit company — and that the two are structured so the arrangement, rather than a pledge, is what keeps the open-standard promise honest.

The structure, plainly

We are building along two tracks that do different jobs.

A nonprofit foundation stewards the standard. It holds the open-source code, defines and maintains the open specification, takes grants, and engages student volunteers for academic credit and service hours. Its purpose is the public interest: the standard exists so that Guatemala — and eventually its neighbors — owns a way of doing algorithmic governance, not a dependency on any one supplier. The foundation is where "cada decisión, a la luz" lives as a governance commitment rather than a tagline.

A for-profit company does the delivery. Implementation, hosting, support, integration, the operational work of standing a system up inside a real institution and keeping it running — that is real, ongoing labor, and it deserves to be paid for. The company can also raise investment, which is how the delivery capacity scales beyond what grants alone would sustain. It competes on how well it implements the open standard, not on owning it.

The division is the whole idea: the thing that must stay public — the standard, the code, the auditability — sits with the nonprofit; the thing that is genuinely a service — building and running deployments — sits with the company.

Why both, rather than one

A pure charity could hold the standard beautifully and struggle to deliver at scale. Grants are episodic; implementation and hosting are continuous. A foundation trying to run production systems on grant cycles is a foundation perpetually one funding gap away from an outage — not a foundation citizens should depend on for a benefits system.

A pure company could deliver capably and would face a permanent temptation to close what should stay open. The commercial logic of a lone for-profit almost always bends toward lock-in, because lock-in is where the margin is. Even with the best intentions, a single company carrying both the standard and the service has put the fox in charge of the henhouse.

Splitting the two removes the temptation by construction. The company cannot lock in a government by capturing the standard, because it does not hold the standard — the nonprofit does, in the open, under a license anyone can read. This is the same instinct that runs through the whole platform: do not rely on a promise where you can rely on a structure. NaciluzIA's core rule keeps binding decisions out of the AI's hands by architecture rather than policy; the hybrid keeps the standard out of the vendor's hands by ownership rather than assurance.

Why sequence the nonprofit and academic track first

Order matters as much as structure. We are starting with the nonprofit and academic side — the foundation, the universities, the open code, the grant-funded and volunteer-built proof — and adding the company later, when paid work or investment actually appears.

This is partly discipline and partly honesty. The proof stage is a three-month MVP for one social program in one municipality, on simulated data. That is exactly the kind of work grants fund and students build for credit; it does not need a commercial entity, and standing one up prematurely would invite the wrong incentives before there is anything to sell. The company earns its existence when there is real delivery to be done — a live pilot, a real institution, a contract or an investor. Building the for-profit arm first would be putting the storefront up before the thing in the window is real.

Sequencing this way also keeps the founding story straight. When the company arrives, it arrives into a world where the standard is already open, already stewarded by the foundation, already built partly by the universities. It joins a public thing; it does not privatize one.

The promise this protects

"Open standard, not a vendor" is easy to say and hard to mean. The hybrid is how we intend to mean it: the code and the specification live in a nonprofit whose reason to exist is to keep them open, and the commercial work lives in a company that competes on service without ever owning the thing everyone depends on. A government adopting NaciluzIA adopts a standard it can inspect, fork, and outlive its supplier with — and can hire our company, or someone else's, to implement.

One note in fairness: this is a description of our intent, not legal or tax advice. Anyone designing a comparable structure should confirm the specifics with local counsel, because the right vehicles and rules vary by jurisdiction.

We chose both because the public interest needs a guardian that will not be tempted, and delivery needs a business that can be paid. Kept separate, and sequenced honestly, the two let us build something fast and sustainable without ever quietly becoming the vendor we told everyone we were not.

Cada decisión, a la luz.

— Anushka Appala and Dr. Janio Rosales