Anyone Can Create Software — And It's Changing the World
For most of history, the ability to create software was gated behind years of formal training, access to expensive tools, and development budgets that placed it out of reach of most people and organisations. Three forces — AI-assisted coding, open-source infrastructure, and near-zero deployment costs — have collapsed that barrier faster than most observers anticipated. This piece looks at what the democratisation of software creation actually means: the economic consequences for businesses, the equity implications for developing countries, the public sector opportunity, and the real projects already proving the case.
The Barrier to Creating Software Has Collapsed
The barrier to creating software has not just lowered — it has fundamentally changed in character. The old barrier was primarily one of credential and expertise: you needed years of formal training to acquire the knowledge required to build something that worked. The new landscape has not eliminated the value of deep technical expertise, but it has separated the threshold required to build something useful from the threshold required to become a professional software engineer. Those are now different things, and the first is within reach of anyone motivated enough to pursue it.
Three forces are driving this simultaneously. AI-assisted coding tools translate plain-English problem descriptions into working code with sufficient quality that a person with no prior programming experience can produce something functional from day one. The learning curve is not eliminated — understanding what the code is doing, debugging when it fails, and iterating toward a better solution still require developing knowledge — but the steep initial gradient that previously required years of structured study to climb is now traversable much faster. The distance between understanding a problem and being able to encode a solution has shrunk dramatically.
Open-source infrastructure provides a second enabling force. The vast ecosystem of freely available libraries, frameworks, databases, authentication systems, and deployment tools means that new creators are not starting from zero — they are starting from a foundation that the global development community has built and refined over decades. The Linux operating system, PostgreSQL, React, Node.js, Docker, and hundreds of other production-grade tools are free to use and build on. A solo developer or a small team gets access to the same technical infrastructure that powers some of the world's largest applications, at no cost.
The third force is the collapse of deployment costs. In the early internet era, putting software into production required owning or renting physical server hardware, managing networking infrastructure, and maintaining the physical plant. Cloud computing eliminated most of that, but even five years ago a production-grade deployment could easily cost hundreds of dollars per month before the first user logged in. Today, a working application serving real users can run for $5 to $20 per month on modern cloud infrastructure, with no capital expenditure and no technical operations burden beyond a basic understanding of how to configure a server. The financial risk of building and deploying something has been reduced to approximately zero.
What It Actually Means When Anyone Can Create Software
When we say anyone can create software, the claim is not that everyone will become a professional software engineer. It is something more specific and more important: the ability to translate a real-world problem into a working digital solution is no longer gated by access to a development team with a large budget. A person with deep domain expertise in their field — medicine, agriculture, education, logistics, construction — can now build tools that encode that expertise in ways that were previously only achievable by organisations that could afford professional development.
The practical implications are wide. A nurse who spots an inefficiency in patient handover can prototype a digital checklist application. A teacher frustrated by assessment administration can build the tool they have always wished existed, tailored to their classroom rather than a vendor's generic model. A farm manager wanting to track livestock health across multiple paddocks can create a lightweight database application that fits their land and their workflow. A small business owner can replace a $500-per-month SaaS subscription with a system they own outright and can adapt as their needs change.
What unites these examples is that the value comes from the creator's domain knowledge, not from their technical training. The software creation tools are now good enough that domain expertise is the primary input — the technical implementation is the learnable accompaniment rather than the prerequisite. That inversion is the real significance of the democratisation. It means that the people who understand problems most deeply are now the people best positioned to build the solutions, rather than having to translate their understanding to a third party who builds something that approximates it.
What Cheaper, More Accessible Software Means for Society
The democratisation of software creation has consequences that extend well beyond individual productivity gains. When software becomes dramatically cheaper and more widely buildable, the effects propagate through economic structures in ways that compound over time.
Small Businesses Reclaim Margin and Operational Control
Enterprise software pricing has historically been set by vendors with significant market power, who could charge what the market would bear because alternatives were scarce. As open-source alternatives reach production quality across every major business software category — ERP, CRM, accounting, project management, HR — the leverage shifts. A small business that replaces a $500-per-month SaaS subscription with an open-source alternative it owns outright reclaims that margin directly. Multiplied across New Zealand's SME sector, across comparable small business populations in Southeast Asia and the Pacific, the aggregate economic effect of even partial substitution is substantial. The money that was flowing to software vendors in San Francisco or Seattle stays in local economies.
Developing Nations and the Pacific Access Enterprise-Grade Tools
The price barrier for enterprise software has historically excluded organisations in lower-income countries from the tools that drive scale and efficiency. A healthcare NGO in Fiji, a cooperative agricultural network in Samoa, or a local government in Tonga did not have access to the same operational infrastructure as their counterparts in wealthy countries — not because the technology was unavailable, but because the pricing model placed it out of reach. Open-source software changes this equation entirely. The code that runs an enterprise-grade government platform or a production ERP system is the same everywhere. The only costs are hosting and the human capability to deploy and maintain it. Those costs are now within reach of organisations that were previously excluded from this tier of operational infrastructure.
Public Sector Budget Flows to Services, Not Vendor Licenses
Government agencies and public institutions are chronically overcharged by large enterprise vendors for systems that are inflexible, expensive to maintain, and designed around the vendor's commercial interests rather than public service requirements. France, Germany, and Estonia have made substantial moves toward open-source government infrastructure — and the financial and operational results have been documented and significant. When a local council can deploy a digital services platform for the cost of modest cloud hosting rather than a six-figure annual license, the difference is budget that flows into frontline services rather than software vendor profits. At scale across the public sector, this represents a meaningful reallocation of public money.
Innovation Accelerates at the Edges
The most valuable innovations rarely originate in headquarters. They come from the people closest to the problems — the district nurse who sees the gap in patient handover systems, the regional council planner who understands why current case management tools do not map to local conditions, the cooperative farm manager who knows what a livestock tracking system would need to do to be actually useful. When those people have the tools to build solutions themselves, the pace of innovation across healthcare, education, agriculture, and conservation accelerates dramatically. The bottleneck was never the quality of ideas at the edges — it was the inability to translate those ideas into working software without a large budget and a professional development team.
Real Proof: What Democratised Software Creation Looks Like in Practice
Abstract arguments about democratisation are only as convincing as the concrete evidence behind them. The most direct evidence is specific projects: things that exist, that work, that are in use, and that were built by individuals without corporate budgets. The TPT Solutions open-source hub provides exactly this kind of evidence.
TPT Free ERP is a fully modular, open-source enterprise resource planning system built in PHP with a PostgreSQL database. It includes a complete REST API layer, database migration tooling, email templating, CI/CD automation via GitHub Actions, Docker deployment support, and a codebase following modern software engineering standards. It is MIT licensed. The use case is direct: a small New Zealand manufacturing or wholesale business currently paying $800 per month for a commercial ERP subscription that covers perhaps 70% of their actual workflow can deploy TPT Free ERP tailored exactly to their processes, for the cost of a modest cloud server. The subscription cost disappears. The system is owned outright. The code is modifiable by any developer as the business evolves.
The TPT Government Platform addresses a different category of institutional challenge. Digital government is a global problem: public agencies are trapped in expensive, inflexible enterprise systems that cost enormous sums to license and maintain, deliver poor citizen experiences, and are designed around vendor commercial interests rather than public service requirements. The TPT Government Platform is a production-grade alternative: AI-powered document processing, multi-factor authentication including biometric WebAuthn passkeys, drag-and-drop workflow automation, multi-tenancy across government departments, 50+ language support, WCAG 2.1 AA accessibility compliance, and Progressive Web App capability for offline and low-bandwidth deployment. Deployable in under five minutes via Docker. Hosted for under $20 per month. MIT licensed.
Both projects were built by a single developer, building in public, and given to the world for free. That is what the democratisation of software creation looks like when it is operating at full stretch: production-grade infrastructure that would previously have required corporate budgets and professional teams, built by an individual, available to anyone. The 22-repository ecosystem at TPT Solutions — covering game engines, desktop editors, decentralised social platforms, and transport management systems alongside the ERP and government tools — extends the demonstration across domains, consistently making the same point.
TPT Solutions: Software Built for the People Who Do the Work
TPT's field service platform is built on the same philosophy as its open-source work: software should fit the people who use it, not the other way around. Purpose-built for trade businesses in New Zealand and Australia — electricians, plumbers, builders, and the full range of field service trades — it brings the same quality of operational thinking to the businesses that power local economies.
Start Free TrialHow Society Can Accelerate This Shift
Recognising that anyone can create software is one thing. Building the conditions that make it universal — that make the capability genuinely accessible across income levels, geographies, and educational backgrounds — is another. Each stakeholder group in the ecosystem has a distinct role.
Start before you feel ready
The most important thing any aspiring creator can do is begin. Use AI tools to help you build something small that solves a problem you personally face. Share it on GitHub. Iterate. The first project will be imperfect — that is not only acceptable but expected. The skills in software creation compound rapidly once you start, and the global community of people doing this work is genuinely generous with knowledge and support. The barrier to entry has collapsed; the remaining barrier is the decision to start.
Treat software capability as a core competency
Forward-thinking organisations are recognising that software capability cannot be entirely outsourced. Investing in training staff to build and adapt digital tools — even at a basic level — creates compounding operational value. An operations manager who can automate a workflow, or a data analyst who can build a custom reporting dashboard, generates leverage that a vendor subscription never can. The capability is an asset that stays inside the organisation, improving over time, rather than a recurring cost that stays with the vendor.
Embed software creation across every discipline
Software literacy is now as fundamental as writing and numeracy. Schools and tertiary institutions should integrate software creation into every subject area — not just computer science. A biology student who can build a data visualisation tool is more capable in the modern economy than one who cannot. A commerce student who can prototype a marketplace app understands their field differently. The framing of software creation as a specialist credential rather than a general capability is increasingly at odds with what the economy demands.
Fund open-source infrastructure as public investment
Every dollar spent on high-quality open-source software creates value distributed across the entire economy — not captured by a single vendor. Governments should treat open-source contribution the same way they treat investment in roads, research institutions, or broadband infrastructure: as essential public goods that generate returns far exceeding their direct cost. The countries that have made this investment — in digital infrastructure, in developer education, in open-source public service platforms — are measurably ahead of those that have not.
The Bigger Picture: Agency, Power, and What Gets Built
For most of human history, the tools that shaped how society operated — printing presses, broadcast infrastructure, digital platforms — were controlled by whoever had the capital to build and own them. That concentration of tool-making power in the hands of capital had profound consequences for economic opportunity, information access, and civic participation. The people who needed tools built for their specific contexts were largely dependent on whether those contexts were large enough or profitable enough for a vendor to care about.
A world where anyone can create software is a world where those tools are genuinely distributed. A community in regional Northland can build the digital platform it needs without waiting for Wellington to prioritise it. A Pacific Island health ministry can deploy world-class government software without waiting for an enterprise vendor to develop a Pacific edition. A social enterprise can build exactly the right tool for its mission without compromising to fit a vendor's product roadmap that was designed for a different kind of organisation entirely.
The open-source projects being built right now — including the work at TPT Solutions — are proof that this is not aspirational. It is happening. The gate is open. The question is not whether anyone can create software. The question is how broadly that capability gets extended, how deliberately we invest in the education and infrastructure that makes it accessible beyond the already-technical, and what the world looks like when every community and every organisation has the capability to build the tools it actually needs.
Frequently Asked Questions
Can anyone really create software without a computer science degree?
Yes — and this is no longer a speculative claim. AI-assisted coding tools, open-source frameworks, and modern no-code and low-code platforms have collectively lowered the entry barrier to the point where people with no prior programming experience are building real, working applications. The shift is not about removing the need for all technical knowledge — it is about reducing the barrier to entry low enough that motivated people with domain expertise can create tools that solve real problems in their fields. The remaining learning curve is meaningful but it is no longer prohibitive, and it is getting shallower with every generation of AI tooling.
What is open-source software and why does it matter for democratisation?
Open-source software is software whose source code is publicly available for anyone to inspect, use, modify, and distribute, typically at no cost. It matters for democratisation because it means that every new creator does not start from zero — they start from a foundation of high-quality infrastructure that the global community has already built. The Linux operating system, the PostgreSQL database, the React framework, the thousands of libraries available through package managers: all of this is freely available to anyone who wants to build on it. That standing foundation is worth billions of dollars in equivalent development work, and every creator gets access to it for free.
How does AI change the ability for non-developers to create software?
AI coding assistants reduce the most significant barrier non-developers face: the requirement to know specific syntax, APIs, and idiomatic patterns before being able to produce working code. A person with a clear understanding of the problem they want to solve and the logic of how to solve it can now describe that problem in plain language and receive working code that implements it. They still need to understand what the code is doing well enough to verify and iterate on it — which requires learning — but the threshold of required knowledge before being able to produce something useful has dropped dramatically. The result is that domain expertise becomes the primary input, with technical implementation as a learnable accompaniment rather than a prerequisite.
What is TPT Free ERP?
TPT Free ERP is a free, open-source enterprise resource planning system built and published by TPT Solutions. It is a full-stack application built in PHP and PostgreSQL with a modular architecture, REST API layer, Docker deployment support, database migration tooling, and an MIT licence — meaning it can be used, modified, and deployed by anyone at no cost. It is available on GitHub and is designed to give small and medium businesses access to ERP capability that was previously only affordable for large organisations paying five- or six-figure annual licenses for commercial alternatives.
What is the TPT Government Platform?
The TPT Government Platform is a free, open-source digital government services platform built by TPT Solutions for modern public agencies. Its feature set is production-grade: AI-powered document processing, multi-factor authentication including biometric WebAuthn passkeys, drag-and-drop workflow automation, multi-tenancy for multiple government departments from a single installation, 50+ language support with RTL compatibility, full WCAG 2.1 AA accessibility compliance, and Progressive Web App capability for offline and low-bandwidth contexts. It can be deployed in under five minutes via a single Docker command, with hosting starting below $20 per month on a compliance-certified provider.
How does open-source software help businesses in developing countries?
The price barrier for enterprise software has historically excluded organisations in lower-income countries from the operational infrastructure that drives efficiency and scale. Open-source software removes that price barrier entirely — the code is free to use and the only costs are hosting and the human capability to deploy and maintain it. For a Pacific Island health ministry, a Southeast Asian cooperative, or a community organisation in sub-Saharan Africa, access to production-grade open-source ERP, government platform, or data management tools represents genuine capability that was previously inaccessible. The democratisation of software creation is, in part, a story about global economic equity.
Why is software pricing so high, and will it come down?
Software pricing has historically reflected artificial scarcity — the scarcity of people who could build it, the monopoly power of vendors who owned the market, and subscription models that extracted perpetual rent once a business was dependent on the tool. As more high-quality open-source alternatives proliferate at every layer of the software stack, and as more people gain the capability to build purpose-fit tools themselves, that artificial scarcity erodes. The direction is clear: software prices are trending down across most categories as competition increases and open-source quality improves. The pace is uneven — some categories are further along than others — but the structural pressure is consistent and compounding.
What is the difference between no-code, low-code, and custom-built software?
No-code tools allow users to build applications through visual interfaces without writing any code — they are fast to start with but constrained by what the platform supports. Low-code tools provide visual interfaces augmented by code for customisation — more flexible than no-code, but still operating within a platform's architecture. Custom-built software is written directly in programming languages against infrastructure you own and control — maximally flexible but requiring more technical capability to build and maintain. AI coding tools are increasingly blurring the boundary between these categories, enabling people to write custom code with assistance that bridges the gap between their domain knowledge and technical implementation.
Is it ethical to release software for free — does it undermine developers' livelihoods?
The open-source ecosystem has produced some of the most technically skilled and well-compensated software developers in the industry. The Linux Foundation, Mozilla, PostgreSQL, Apache, and thousands of other open-source projects are maintained by developers who are employed specifically to work on these codebases, or who build commercial businesses around their open-source work. Open-source does not eliminate the market for developer skill — it redirects that skill toward higher-value work: building on top of shared infrastructure rather than re-implementing the same foundations repeatedly. The developers most at risk from the democratisation of software creation are not the skilled professionals building complex systems; they are those whose value was primarily the scarcity of their access to tools, which is different from the scarcity of their expertise.
Can open-source software be trusted for business-critical operations?
The world's most critical digital infrastructure runs on open-source software. The internet itself runs on open-source protocols and software stacks. The majority of cloud infrastructure is built on Linux. PostgreSQL, MySQL, and other open-source databases handle billions of transactions per day in production environments. The question of whether open-source software can be trusted for business-critical operations was settled a long time ago — the answer is unambiguously yes. What requires judgment is choosing well-maintained, actively developed projects with good documentation and active communities over abandoned or poorly supported alternatives. That judgment is straightforward to apply with basic due diligence.
How can governments benefit most from the open-source software movement?
Governments benefit in three distinct ways. First, direct cost savings: replacing expensive commercial licenses with open-source alternatives for the software governments use internally redirects budget from vendor payments to public services. Second, capability ownership: open-source software can be modified and extended by government IT teams or local contractors, reducing dependency on vendors who may not prioritise public service requirements. Third, civic transparency: open-source government platforms allow citizens and independent auditors to inspect the code that processes their data and manages their services — a democratic accountability dimension that proprietary systems cannot offer. The countries furthest ahead in digital government are disproportionately those that have invested most heavily in open-source public infrastructure.
What role does the TPT Solutions open-source hub play in this movement?
The TPT Solutions open-source hub is a concrete demonstration of what is possible when individual developers build in public and share their work freely. With 22+ public repositories covering ERP systems, government platforms, game engines, desktop editors, decentralised social platforms, and transport management tools, it shows that production-grade software across diverse domains can be built without corporate budgets and given to the world at no cost. It is both a set of genuinely useful tools and a proof of concept for the proposition that the democratisation of software creation is real and already delivering results — not a future possibility, but a present reality.
Software That Works for the Businesses That Build New Zealand
TPT Solutions builds purpose-fit software for trade businesses: electricians, plumbers, builders, and the full range of field service trades across New Zealand and Australia. Job management, quoting, invoicing, compliance documentation, and scheduling — designed around how tradespeople actually work, not how generic business software assumes they do.
See the Platform