---
title: "Custom Software"
description: "We build document workflows, customer portals and connections between your existing systems. We also maintain and operate the applications we deliver."
url: https://www.alt-f1.be/en/custom-software/
organization: ALT-F1 SRL, Brussels (VAT BE 0830.560.718)
---

# Custom Software

We build document workflows, customer portals and connections between your existing systems. We also maintain and operate the applications we deliver.

## What we can build

- Replace repeated manual work with software designed for your organisation.
- Connect existing business systems so information does not have to be entered twice.
- Agree delivery, ownership, operation and maintenance before the project starts.

## Applications built by ALT-F1

- **PolyDocs** — Control an application using voice commands.
- **Video-To-Chapter** — Turn a recorded meeting or course into searchable summaries.
- **Facility Management** — Plan, validate and follow work on site.
- **Digital offers & policies** — Prepare and sign offers and policies, with a digital payment flow.
- **The Accelerator** — Collect and analyse public web information for business and research teams.
- **Broadcast & SIP Secure** — Run broadcast workflows and protect internet voice, video and messaging.
- **Connectivo** — Manage customer conversations and automated replies across messaging channels.
- **StratEx** — Track programmes, projects, contracts and board reports together.
- **Cloud migration** — Plan the move of applications to a suitable hosting setup.
- **IT Service Management** — Organise support requests, incidents and changes with an inventory of systems.

We have worked for public administration (Smals, Europol, Eurojust, European Commission DGs, Federal Police), broadcasting (BBC, WDR, YLE, VT4), telecom and retail (KPN, Orange, Galeria INNO, Tale Me), industry and transport (BMW, Toyota, DAF Trucks, SNCB/NMBS, Sonaca, Asco), banks and insurance (Argenta, BNP Paribas Fortis, AXA, NN, Patronale) and health (NovInject): delivered, and supported for years.

## How it works

1. Define the users, the task and what a successful result looks like.
2. Build and review changes, then run checks before releasing them.
3. Monitor the application, keep records of its components and test recovery.

**Build, release and maintain your application.**

### Develop and document your software

- Keep a history of code changes
- List the software used and check its versions

### Review and release

- Review and test each change
- Release the approved version

### Maintain and recover

- Track components and flaws
- Back up and test recovery

A controlled delivery process, with checks and recovery planned from the start.

- **Repository** — the one place that holds the code, the settings and the encrypted secrets of your application, with their whole history
- **Pinned version** — every building block named with its exact version, so the same thing runs tomorrow as today; a change is a proposal you can read first
- **Merge** — the moment a reviewed change joins the main line; nothing reaches the server without it
- **Deploy script** — one short program that puts the new version on the server the same way every time, and puts the old one back if the check fails
- **[SBOM](https://www.alt-f1.be/en/acronyms/#sbom)** — Software Bill of Materials. the list of every package inside the application, checked against the known vulnerabilities
- **[CMDB](https://www.alt-f1.be/en/acronyms/#cmdb)** — Configuration Management Database. one file that says what runs where: application, server, address, port, backup
- **Backup rehearsal** — a backup is only real once it has been restored; we restore on a schedule, not on the bad day

<a id="why-it-is-in-the-stack"></a>

## How we deliver and maintain your application

We agree the work in manageable steps. Each change is reviewed and checked before release, with a repeatable deployment process and a way to return to the previous version.

An inventory records the software components and deployed systems. Backups and restore tests are planned with the application’s availability and recovery needs. The [delivery film](/en/film/#pipeline-h) follows this process.

<a id="handover"></a>

## Your code, records and handover

Your project includes the source-code and operational records agreed in the contract. We document how to release a change, manage access and restore the service.

We agree who owns each responsibility during delivery and afterwards, including maintenance, security updates and support. Technical implementation details are available below.

**Technical details:** For IT people: infrastructure as code, pinned dependencies, secrets encrypted in git, SBOM and CMDB, one pipeline from commit to production.

## Training for your team

- Length: One day
- For whom: Project leads, purchasing and IT teams
- On the programme: Review delivery, maintenance and handover requirements.

## Related security topics

- SOFTWARE [Build software securely](https://www.alt-f1.be/en/table/sd.md)
- VULN [Find and prioritise weaknesses](https://www.alt-f1.be/en/table/vm.md)
- CLOUD [Secure cloud accounts and storage](https://www.alt-f1.be/en/table/cl.md)
- CRA [Security of software products](https://www.alt-f1.be/en/table/cra.md)
- TEST [Test security with permission](https://www.alt-f1.be/en/table/pt.md)