Skip to content
APFerrer
Software licensing

Software and modules you can license, rebrand or build into your product

This is a catalog of 24 products and 19 modules that I license to other companies. You can take the source code and adapt it with your own team, run a product on your infrastructure under your brand, or embed a module in the software you already ship. I keep ownership of the code. You get the rights we agree on, in writing, and exclusivity for your industry or territory if you need it.

I'm Aida P. Ferrer, a Forward Deployed Engineer based in the Canary Islands, Spain. I license to companies in the EU, the US and elsewhere.

Price upon request, based on license type and scope · Reviewed: November 2026

complete products
24
complete products
embeddable modules
19
embeddable modules
license types
5
license types
License types

What each license type is and what you get

Price upon request, based on license type and scope. Maintenance and support are always contracted separately.

Source code license

You get the code and the right to modify it, so your team can adapt it to your processes and maintain it. Ownership stays with me. The contract sets out what you can do with the code, where, and for how long.

  • The complete source code of the asset
  • Installation and configuration documentation
  • A technical handover session with your engineers
  • A warranty against defects for the agreed period
  • The right to modify and use it within the scope of the license

White-label or on-premise license

The product is installed on your servers or in your cloud account under a license to use it. With white label it carries your name, logo and domain, and your users never see mine. It does not include rights to the source code.

  • The software installed on your infrastructure
  • Initial configuration with your real data
  • Training for the people who will run it
  • Your brand on the interface, if you choose white label

Embeddable module license

A component you build into your own software: a connector, a rules engine, a security or billing layer. You get the piece your product needs without designing it and owning its upkeep from day one.

  • The module's code, ready for you to integrate
  • Any installation scripts it needs
  • Integration examples and documentation
  • A warranty against defects for the agreed period

OEM license

For software vendors that ship an asset inside their product and distribute it to their customers as part of that product, with no approval needed for each installation.

  • The right to integrate it into a commercial product of yours, named in the contract
  • The right to distribute it within that product, with no cap on end customers unless agreed
  • Non-exclusive by default
  • No reselling or sublicensing the asset on its own

Sector or territory exclusivity

This is a term you add to a source code or white-label license, not a license type on its own. I commit in the contract not to license that asset to anyone else in the industry or territory we agree on, for the agreed term.

  • By industry, territory or both
  • For a fixed term
  • Each asset page says whether it is available

Full acquisition

The one case where the buyer ends up owning everything: the code, the intellectual property and the know-how. Only one asset is offered this way today, AXIOM.

See AXIOM
How it works

From first request to signature

Not everything is shared at once. What you see on this site is public. The rest comes in stages, as the interest firms up and once a confidentiality agreement is signed.

  1. 01

    Request

    Fill in the form with the asset reference, the license type you have in mind and what you plan to do with it. If you'll need to see code, tick the NDA box.

  2. 02

    First reply

    I answer in writing with the questions I need to judge fit: intended use, industry, territory, whether you want exclusivity.

  3. 03

    Asset brief

    If there's a fit, you get the qualified-buyer brief: detailed functional scope, license types, general terms and pricing for your case.

  4. 04

    Mutual NDA and technical review

    Once both sides have signed, your engineers go through the documentation and the code, in a guided session or with temporary read-only access.

  5. 05

    Proposal and negotiation

    A written proposal covering license type, scope, territory, term and warranty. Support and maintenance come as a separate proposal.

  6. 06

    Contract and signature

    The license terms are set out in writing in the contract we sign.

  7. 07

    Delivery and handover

    You receive the code, the installation or the module, depending on the license, with its documentation and a handover session.

LevelWhenWhat you see
PublicAlways, on the asset pageWhat it does, who it's for, license types, technical specifications, requirements and integrations
Qualified buyerAfter the first replyAsset brief, general terms and pricing for your case
Under NDAOnce the mutual NDA is signedTechnical documentation and code review
NegotiationAfter the reviewProposal and draft contract

AXIOM follows its own process, conducted entirely in writing. Its page explains it.

License or build

A license starts with something that already exists

A new build starts with a spec and a promise. A license starts with something that already exists: your team reviews it before you sign and knows exactly what it's getting.

  • Your engineers spend their time on what sets your product apart. The parts every product needs (billing, connectors, audit trails, deadline alerts) are already written.
  • The license cost is agreed before work starts. The real cost of a build from scratch shows up at the end.
  • With a source code license the knowledge stays in-house. You don't need me for every change.
  • With exclusivity, no one else in your industry or territory can license the same asset while the contract runs.

There are trade-offs, and you should hear them up front. Except for AXIOM, you don't become the owner. Integrating an asset into your systems takes work, less than writing it, but it isn't zero. And with an installation-only license, how the product evolves depends on what we agree.

If what you need is someone to adapt a product to your operation and leave it running, that's a different service: Custom Vertical Software.

Industry context

10%

projected growth in US software developer employment between 2025 and 2035, with about 106,100 openings a year on average.

US Bureau of Labor Statistics, Occupational Outlook Handbook, Software Developers

57.5%

of EU companies that hired or tried to hire ICT specialists had trouble filling those roles.

Eurostat, ICT specialists: hard-to-fill vacancies in enterprises (reference year 2023)

76%

of AI use cases were bought rather than built in-house, in a survey of 495 US enterprise AI decision-makers.

Menlo Ventures, 2025: The State of Generative AI in the Enterprise (December 2025)

68%

of the commercial codebases audited had open source license conflicts, up from 56% a year earlier.

Black Duck, Open Source Security and Risk Analysis 2026

General figures from public sources. They are not results of any asset in this catalog.

FAQ

What buyers usually ask

  • Do I own the code?

    Not unless it's AXIOM. For every other asset I keep ownership and you get a license: the contract defines what you can do with it, in which territory, for how long, and whether it's exclusive. If you need full ownership of the code and IP, that's an acquisition, and today only AXIOM is offered that way.

  • Source code, white label, embeddable module or OEM: which one do I need?

    If your team will change the product itself, take the source code license. If you want to run it under your own brand without touching the code, white label is enough. If you only need one component inside your own software, take the embeddable module license. OEM is for vendors who ship that component to their customers as part of their product.

  • Can I get exclusive rights?

    For assets that allow it, yes. Exclusivity can cover an industry, a territory or both, for a fixed term. While it runs, I don't license that asset to anyone else within the agreed scope. Each asset page says whether exclusivity is available.

  • Can my team review the code before we sign?

    Yes, under a mutual NDA. Your engineers go through the documentation and the code in a guided session or with temporary read-only access, and ask their questions before we get to contract terms.

  • Are maintenance and support included?

    No. Every license type comes with a warranty against defects for the agreed period. Maintenance (updates and bug fixes) and support (questions, training, adaptations) are separate contracts, and you can skip them if your team takes over.

  • Will you be our data processor under the GDPR?

    Only if you need me to be. If the software runs on your infrastructure and I have no access to the data, you are the controller and I process nothing on your behalf. If you contract support that requires access to personal data, we sign a data processing agreement under Article 28 of the GDPR.

  • What changes under the EU AI Act and the Cyber Resilience Act if I put my brand on it?

    In both laws, the company whose name or trademark is on the product carries the main obligations. Under the AI Act, whoever places an AI system on the market or puts it into service under its own name is the provider (Articles 3 and 25). Under the Cyber Resilience Act, the company that markets a product with digital elements under its own name or trademark is its manufacturer. With white label or OEM, that may be you. Each asset page says which parts use AI, and I provide the technical documentation you need for your own assessment.

  • We're outside the EU. Can we license?

    Yes. I license to companies in the US and other non-EU countries. The whole process, from the first request to the contract, is handled in writing.

Request

Tell me what you're looking for

Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.

Controller: APFerrer. Purpose: to answer your request. You can exercise your rights as described in the privacy policy.

Price upon request, depending on license type and scope. Maintenance and support are contracted separately.