Jasmine Business Directory

Software is the set of instructions, data, and programs that tells a computer what to do, in contrast to the hardware on which those instructions run. The word covers a wide range of things: the operating system that manages a machine, the applications people open to write documents or edit images, the embedded code inside a car or a thermostat, and the back-end services that keep websites and mobile apps running. Because the term is so broad, this category groups together the companies, products, and resources that build, sell, or support computer programs of many kinds. A software web directory like this one is meant to make that breadth easier to work through, so a visitor can move from a general interest down to a specific vendor or tool without wading through unrelated results. The page works better read as a sorted software directory than as a flat list, since the grouping already does some of the filtering for you.

The discipline that produces software in a structured way is usually called software engineering. The IEEE defines it as the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software (IEEE, 1990). That definition matters because it draws a line between writing a quick script and building a product that other people depend on. The second kind of work needs planning, testing, documentation, and a way to handle change over time. Most of the businesses listed in a software business directory operate on that second footing, where reliability and support are part of what is being sold.

The field did not always have a name. The phrase software engineering was popularised at a conference sponsored by the NATO Science Committee, held in Garmisch, Germany, in October 1968 and chaired by Friedrich L. Bauer. The report that followed, edited by Peter Naur and Brian Randell, described what the attendees called a software crisis: projects ran late, costs were underestimated, quality was poor, and demand for capable programmers outstripped supply (Naur and Randell, 1969). Many of the problems they listed are still recognisable today, and the conference is often cited as the start of software engineering as a named discipline.

Academic reflection on the subject grew over the following decade. Frederick P. Brooks Jr., who had managed the development of IBM's System/360 operating system, set out hard-won lessons about large projects in The Mythical Man-Month (Brooks, 1975). His best-known observation, that adding people to a late project tends to make it later, became shorthand for the way communication overhead scales faster than headcount. Texts like that one helped turn software from a craft passed between practitioners into a body of knowledge that could be taught and studied.

That body of knowledge was eventually written down in a formal way. The Guide to the Software Engineering Body of Knowledge, prepared by the IEEE Computer Society and adopted as a technical report by the International Organization for Standardization and the International Electrotechnical Commission, divides the field into knowledge areas such as requirements, design, construction, testing, and maintenance (ISO/IEC, 2015). For anyone trying to understand the listings here, those knowledge areas are a useful map: a firm may specialise in one of them, such as testing, or claim to cover the whole life cycle. Reading a vendor's description against that map is a quick way to judge what it actually offers.

It helps to separate a few overlapping ideas that newcomers often blur together. A program is a single piece of executable code. An application is a program, or a set of them, aimed at a task a person wants to accomplish. A platform is something other software is built on top of, such as an operating system or a database. A service, increasingly, is software you reach over a network rather than install yourself. The categories used in this software business directory tend to follow these distinctions, which is why the same company can appear under more than one heading depending on what part of its work is being described.

Most software is produced through a sequence of activities often called the software development life cycle. The classic description breaks the work into stages: gathering requirements, designing the system, writing the code, testing it, releasing it, and then maintaining it once people are using it. These stages give teams a shared vocabulary and a way to know what comes next. They also make it possible to estimate effort and to spot, at least roughly, where a project has stalled. The vendors gathered in a software business directory frequently describe their process in these terms, because clients want to know how a job will be run before they commit to it.

The first widely cited model arranged those stages in a strict line, each one finishing before the next began. This linear approach is usually called the waterfall model, and it is often traced to a 1970 paper by Winston W. Royce, although Royce himself warned that running the stages purely in sequence was risky and argued for feedback between them (Royce, 1970). The model suits work where the requirements are well understood and unlikely to shift, such as some regulated or safety-critical systems. Its weakness shows when requirements change midway, because going back to an earlier stage is expensive once later work has been built on top of it.

A reaction to those rigidities took shape at the start of the 2000s. In February 2001, seventeen practitioners met at a resort in Snowbird, Utah, and wrote the Manifesto for Agile Software Development, a short statement of four values and twelve principles (Beck et al., 2001). It favoured working software over exhaustive documentation, collaboration with customers over contract negotiation, and responding to change over following a fixed plan. Agile did not throw out the life-cycle stages; it ran through them in short repeated cycles, delivering small increments and adjusting as it learned. Frameworks such as Scrum and Kanban put these ideas into day-to-day practice, and many of the development companies catalogued here now describe themselves as agile shops.

Testing deserves separate mention because it is where a lot of cost and risk concentrate. Software can fail in countless ways, from a miscalculated total to a security hole that exposes private data, and finding those faults before users do is its own specialism. Teams use unit tests that check small pieces of code, integration tests that check how parts fit together, and system tests that exercise the whole product. Automated testing lets a team re-run thousands of checks every time the code changes, which is what makes frequent releases safe. A number of the firms gathered on this page exist specifically to test other people's products or to build the tooling that makes testing faster.

Releasing software does not end the work. Maintenance covers fixing defects that slip through, adapting to new operating systems or regulations, and adding features as needs change. Studies of long-lived systems have long shown that maintenance can account for the larger share of total cost across a product's life, which is why support contracts and update policies are such a common part of what software vendors sell. When comparing listings, the maintenance terms often matter more than the feature list on day one: how long a product is supported, and how quickly security patches arrive.

Modern development also rests on a layer of shared infrastructure that did not exist a generation ago. Version control systems track every change to the code and let many people work on the same project without overwriting each other. Continuous integration servers build and test the code automatically whenever it changes, and continuous delivery pipelines push approved changes out to users with little manual effort. Package registries and dependency managers let teams reuse code that others have written rather than building everything from scratch. Reuse is now the norm rather than the exception: a typical application today is mostly assembled from existing components, with original code forming a thin layer on top. Tooling vendors that support these practices make up a fair share of any software web directory, since teams need help managing the parts they did not write.

That reliance on shared components carries real risk. A flaw in a widely used library can affect thousands of products at once, and a compromised package can push malicious code into all of them. The response has been a growing focus on the software supply chain: tracking exactly which components a product contains, often in a software bill of materials, and watching for known vulnerabilities in them. Several specialist firms listed in a software web directory now work entirely on this problem, scanning dependencies and alerting teams when a component they rely on turns out to be unsafe.

One useful way to sort software is by its closeness to the hardware. System software sits nearest the machine and includes operating systems such as Windows, macOS, Linux, Android, and iOS, along with device drivers and utilities that keep a computer running. Application software sits above it and is what most people think of as a program: a word processor, a spreadsheet, a photo editor, a browser, an accounting package. Between the two lies a layer often called middleware, which connects applications to databases, messaging systems, and one another. Most listings fall into one of these bands, and knowing which band a product occupies tells you a lot about who its customers are.

Another common split is by audience. Consumer software is aimed at individuals and households, and it competes on ease of use, price, and design. Enterprise software is aimed at organisations and tends to be larger, more configurable, and sold through longer relationships with support and training attached. Categories such as enterprise resource planning, which ties together finance, inventory, and human resources, and customer relationship management, which tracks a company's dealings with its customers, belong to this second world. Many of the larger names in a software business directory are enterprise vendors, because that segment carries the heaviest spending.

The way software reaches users has changed more than once. For decades, programs were sold as packaged products: you bought a licence, received the program on disks and later on download, and ran it on your own computer. Over the past fifteen years much of the market has moved to a service model, where the software runs on the provider's servers and users reach it through a web browser or an app. The National Institute of Standards and Technology describes this arrangement, Software as a Service, as the capability provided to the consumer to use the provider's applications running on a cloud infrastructure, with the underlying servers and storage hidden from the user (Mell and Grance, 2011). A software web directory increasingly mixes packaged products and hosted services side by side, because many vendors now offer both.

The same NIST work sets out the wider cloud model that software services sit within. It names three service models: Software as a Service, where you use a finished application; Platform as a Service, where you build and run your own applications on a managed foundation; and Infrastructure as a Service, where you rent raw computing, storage, and networking. It also names four deployment models: public, private, community, and hybrid clouds (Mell and Grance, 2011). These terms appear constantly in vendor marketing, and understanding them helps a reader place a listing accurately rather than taking the labels on trust.

Pricing models have shifted alongside delivery. The packaged era favoured a one-time purchase, sometimes with paid upgrades every few years. The service era favours subscription, billed monthly or yearly per user or by usage, which gives vendors predictable revenue and gives customers a smaller upfront cost in exchange for paying indefinitely. There are also freemium products, where a basic tier is free and advanced features cost money, and open-source products, discussed later, where the program itself is free but services around it may be paid. Comparing the true cost of the options listed here means looking past the headline price to how it is charged and what it includes.

Beyond these broad buckets sit countless specialist categories, and the directory reflects that variety. There is software for designing buildings, for editing video, for managing medical records, for running warehouses, for teaching children to read, and for almost any task a computer can help with. Some of it is general-purpose and sold to anyone; some is vertical, meaning it is built for a single industry and assumes knowledge of that industry's rules and habits. Vertical products often command higher prices because they save their buyers from adapting generic tools, and they form a substantial part of the entries serving particular trades.

Mobile software deserves its own note because of its scale. The arrival of smartphones created a vast new category of applications distributed through curated stores rather than sold directly, with the store taking a share of sales and handling payment and updates. Mobile development brings its own constraints: smaller screens, intermittent connectivity, battery limits, and tighter platform rules. A whole industry of studios and tool-makers has grown to address them. Many entries in a software web directory now describe mobile work as a core offering rather than an afterthought, a change from the early years of the platform.

Software is unusual among products because what you buy is rarely ownership of the thing itself. Most programs are protected by copyright, which gives the rightsholder exclusive control over copying, modifying, and distributing the code, and they are sold to you under a licence that grants limited permission to use them (WIPO, 2016). The terms of that permission are set out in an end-user licence agreement, the long document people click past when installing a program. Proprietary licences typically allow you to run the software but forbid copying it, modifying it, reverse-engineering it, or passing it on. Understanding this distinction matters when reading any listing, because an entry for a product is really an entry for the right to use it on stated terms.

A different tradition rejects those restrictions on principle. Free software, as defined by Richard Stallman and the Free Software Foundation, which he founded in 1985, treats freedom rather than price as the point: the freedom to run a program for any purpose, to study and change its source code, to share copies, and to share modified versions (Free Software Foundation, 1996). The closely related open-source movement frames much the same set of permissions in more practical terms, emphasising the development advantages of letting anyone read and improve the code. The Open Source Initiative, founded in 1998, maintains a definition that licences must meet to be called open source. Although the two camps differ in philosophy, their licences overlap almost completely, and the umbrella term free and open-source software, or FOSS, is used when the distinction does not matter.

The licences themselves come in two broad styles, and the difference has real consequences. Permissive licences, such as the MIT and BSD licences, let you do almost anything with the code, including folding it into a closed commercial product, as long as you preserve the original notice. Copyleft licences, of which the GNU General Public License is the best known, go further: if you distribute a modified version, you must release your changes under the same terms, keeping the code open down the chain (Free Software Foundation, 2007). A business weighing an open-source component has to read which style applies, because building on a copyleft component can oblige the firm to open its own code in turn. Plenty of the firms in a software business directory build on permissively licensed code for exactly this reason.

Open-source software is not a fringe concern. It runs much of the internet's infrastructure, from the Linux operating system on most servers to the databases, web servers, and programming-language tools that sit on top of them. Large companies that once treated open source with suspicion now release significant projects under open licences and pay staff to maintain them, partly because shared maintenance of common building blocks is cheaper than each firm reinventing them. Many entries in a software business directory are companies whose product is open source but whose revenue comes from hosting it, supporting it, or selling a hardened commercial edition. For these companies the program is free as in freedom rather than free as in price: anyone may use the code, but the paid service around it is the product.

Patents add another layer, and a contested one. While copyright protects the specific expression of code, a patent can protect an underlying method or process, and software-related patents have been granted for techniques and algorithms in many jurisdictions. Critics argue that broad software patents stifle innovation and feed litigation, while defenders see them as legitimate protection for genuine invention. The boundaries of what can be patented differ markedly between countries, and the law has shifted repeatedly through court decisions. For most readers this is background rather than a daily concern, but it shapes which features competitors can copy and which they must work around.

Data protection law now affects how a lot of software is built and sold. Programs that collect personal information must increasingly meet legal standards for consent, security, and the rights of the people whose data is held, and the rules vary by region. Frameworks such as the European Union's General Data Protection Regulation have set expectations that influence products far beyond their home territory, because vendors prefer to build one compliant system rather than many. Accessibility law adds a parallel obligation, requiring that software be usable by people with disabilities. Listings in business and web directories covering software often flag compliance with these regimes, since for many buyers it is a precondition rather than a bonus.

Security and liability round out the legal picture. As software has moved into banking, healthcare, transport, and critical infrastructure, the consequences of a defect have grown, and so has pressure to hold vendors accountable for it. Some jurisdictions are moving toward rules that make producers more responsible for the safety of the code they ship, a shift from the era when licences disclaimed almost all liability. Independent certification and security auditing have grown into industries of their own as a result. A reader comparing options in a software services directory may find that a vendor's certifications and audit history say as much about its maturity as any feature it advertises.

Software has become one of the largest industries in the world economy. Worldwide spending on information technology was forecast to grow into the trillions of dollars, with software a large and fast-growing share of that total (Gartner, 2026). The market research firm Statista has projected that the United States alone would generate the highest software revenue of any country, running into the hundreds of billions of dollars (Statista, 2025). Behind those numbers sit everything from a handful of dominant platform companies to a long tail of small studios and independent developers, and a curated listing of this kind is one way to see that range laid out rather than only the few names that dominate the headlines.

Several changes are at work in the field at once. The shift to subscription services continues to move revenue from one-time sales toward recurring relationships. Artificial intelligence, and in particular the large generative models that produce text, images, and code, has become both a product category and a tool that changes how software itself is written. Spending on these models has been growing far faster than the wider software market, according to industry forecasts (Gartner, 2026). At the same time, concern about security, privacy, and the concentration of power in a few platforms has drawn the attention of regulators in many countries. All of this shows up in the kinds of companies that appear in business directories that list software firms.

For a visitor, the practical question is how to turn a directory into a shortlist. A reasonable starting point is to define the problem before looking at products: what task must the software perform, who will use it, what it must connect to, and what budget and timeframe apply. With that in hand, the categories here let you narrow from a broad area to a specific niche, and individual listings let you compare vendors on the things that matter: delivery model, pricing, support, and track record. Reading a software directory this way, as a filtered map rather than a ranked list, tends to produce better choices than starting from whichever name is most familiar.

It is worth weighing a few signals that separate dependable suppliers from risky ones. How long has the company existed, and is the product actively maintained with regular updates. What happens to your data if you stop paying, can you export it, and in what format. Is there independent evidence of security practice, such as a recognised certification or a published audit. How responsive is support, and is it included or charged separately. The vendors collected in a software web directory will vary widely on these points, and the answers are usually easier to compare across listings than to extract from a single sales page.

This page gathers companies, products, and resources relevant to software, organised so that related entries sit together and a reader can move between general and specific without losing the thread. The listings span the bands and audiences described above: system and application software, consumer and enterprise tools, packaged products and hosted services, proprietary and open-source offerings. A single search can therefore surface options that a narrower source would miss. Used alongside a clear sense of your own requirements, a software directory of this kind helps turn a vague need into a specific list of vendors worth contacting.

1. IEEE. (1990). IEEE Standard Glossary of Software Engineering Terminology (IEEE Std 610.12-1990). Institute of Electrical and Electronics Engineers
2. Naur, P. and Randell, B. (eds.). (1969). Software Engineering: Report on a Conference Sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968. Scientific Affairs Division, NATO
3. Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley
4. ISO/IEC. (2015). ISO/IEC TR 19759:2015, Software Engineering: Guide to the Software Engineering Body of Knowledge (SWEBOK). International Organization for Standardization and International Electrotechnical Commission
5. Royce, W. W. (1970). Managing the Development of Large Software Systems. Proceedings of IEEE WESCON
6. Beck, K. et al. (2001). Manifesto for Agile Software Development. Agile Alliance
7. Mell, P. and Grance, T. (2011). The NIST Definition of Cloud Computing (NIST Special Publication 800-145). National Institute of Standards and Technology
8. Free Software Foundation. (1996). What is Free Software? (The Free Software Definition). Free Software Foundation
9. Free Software Foundation. (2007). GNU General Public License, Version 3. Free Software Foundation
10. World Intellectual Property Organization. (2016). Understanding Copyright and Related Rights. WIPO
11. Gartner. (2026). Gartner Forecasts Worldwide IT Spending to Grow 10.8 Percent in 2026. Gartner, Inc.
12. Statista. (2025). Software: Worldwide Market Forecast. Statista