Skip to main content
FromNine
Menu

AI Engineering · Enterprise Software · Cloud

Intelligence, built into the way your organisation works.

For ministries, public entities and companies in Malta, we design, build and operate AI systems, enterprise software and cloud platforms, linked to the systems your work already relies on.

  • 2,400+ people
  • 600+ public-sector projects across the EU
  • ISO/IEC 27001 certified
Nine parts that work as one system.

Nine nodes in a three by three grid, joined by one line that traces the FromNine mark. The line runs from business context to intelligence, software, cloud and operations, and ends in a single live system.

  1. 01Business context: Aims, processes and limits
  2. 02–03Intelligence: Data and tested models
  3. 04–05Software: Applications and the links between them
  4. 06Cloud: Platforms and infrastructure
  5. 07–08Operations: Automation that a person supervises
  6. 09Outcome: A single system, live

01 Scale and principles

Large enough to deliver, small enough to answer for it.

We concentrate on AI, cloud and current engineering practice, and we bring the delivery discipline of a large firm to it. For a Maltese organisation this means a team big enough to cover every discipline a programme needs, and the same people from the first design session to the day the system is in daily use.

2,400+people who design, build and operate systems for Government and for private companies.

600+public-sector projects across the EU, completed or still running, for ministries, agencies and other public entities.

400+projects for private companies

Our work with Government and public entities
  1. 01

    Fitted to your existing systems

    We start from the platforms, data and processes you run today and replace only the parts that genuinely need it.

  2. 02

    Built so it can be maintained

    Every system is tested, documented and handed over properly, so that your own staff can still adapt it in five or ten years.

  3. 03

    A person decides where it counts

    Steps with real consequences pause until someone approves them, and each automated action is logged for later review.

  • Summit & Gold Partner for Salesforce, SAP and Odoo
  • ISO/IEC 27001 certification for our information security management
  • Teams working from Antwerp, Ghent and Amsterdam

Some of the organisations we work for

  • Infrabel
  • Fingrid
  • RATP Group
  • ANAS
  • TenneT
  • Enaire
  • Umicore
  • voestalpine
  • Henkel
  • Kingspan Group
  • NXP Semiconductors
  • ESET

together with many other public entities in EU Member States

02 Services

Seven services, one team that answers for them.

AI only pays off when the rest is in place: software that staff are happy to use, data that can be trusted, integrations that do not break and a platform that keeps everything running. We deliver all of these together, so the parts fit and a single team is responsible for the result.

Generative AI that copes with real use: based on your own data, tested before it goes live and monitored while it runs.

  • Search and knowledge systems that follow access rights and quote their sources
  • Testing against quality criteria set together with your staff
  • Live tracking of answer quality, running cost and response time

AI Agents & Automation

Agents that stay inside the rights you grant them and check with a person before any step that matters.

  • Orchestration with limited, defined tool access
  • Approval points and handover to staff
  • A log that traces each action

Data & Analytics

Well-governed data that people and AI can base decisions on.

  • Pipelines with quality controls and traceable lineage
  • Access rules in line with the GDPR
  • Data made ready for search and reporting

Enterprise Software & SaaS

Portals, internal platforms and SaaS products that remain simple to change.

  • Interfaces built to WCAG 2.2 AA
  • Modernisation while operations carry on
  • Automated tests and documentation your staff can work with

Cloud & Platform Engineering

A cloud foundation on which releasing is routine and spending is transparent.

  • Infrastructure as code and environments you can rebuild
  • Delivery pipelines with quality checks
  • Monitoring, recovery plans and clear cost reporting

Integrations & APIs

Systems that pass data to each other dependably, even when one of them fails.

  • API design and event-based integration
  • Field mapping, retries and protection against duplicates
  • Links to CRM and ERP

Architecture & Consulting

A clear technical direction before you commit budget: the options, what each costs you and a roadmap you can justify to your board.

  • Reviews of the architecture you have today
  • Assessed options and recorded decisions
  • Roadmaps with guidance for delivery

Running Salesforce, SAP or Odoo? See our platform work

03 Solutions

From a daily obstacle to a system that works.

We begin with the problem, never with the model. Every example below is set out the same way: what slows your staff down now, the system we propose, the gain you can measure and the point at which a person decides.

01

Document intelligence

Illustrative workflowHow documents come in and are checked
Incoming documents are received, sorted by type, and their fields are extracted and tested against your rules.Cases that fail a check go to a person for review; cases that pass go directly to the business system.
What slows you down
Staff copy details from application forms, letters and attachments into the systems they work in.
What we propose
A managed intake process that sorts each document, pulls out the fields that matter and tests them against your rules.
What you gain
Your staff deal with the unusual cases, not the routine ones.
Where a person decides
When the system is unsure, a person checks the case before anything is written to the business system.
Read about document intelligence
02

Enterprise knowledge

Illustrative workflowKnowledge search that follows access rights
Document libraries, wikis and tickets are indexed along with their access rights, and the content owners decide what goes in.Retrieval that follows those rights returns an answer with its sources, and user feedback improves it. Both index and retrieval stay within an access boundary.
What slows you down
The answer is somewhere in the organisation, yet staff can spend hours looking for it.
What we propose
An assistant that searches and answers, shows each user only what their access rights allow, and gives the source of every answer.
What you gain
Answers that come quicker, stay consistent and can be checked.
Where a person decides
Each answer points to where it came from, and the owners of the content choose what gets indexed.
Read about enterprise knowledge
03

Service assistance

Illustrative workflowHow service assistance works
Each request is read for its purpose and background, and the assistant proposes a reply together with relevant knowledge.A member of staff adjusts and sends the reply, sensitive matters go to a specialist, and the CRM record is brought up to date.
What slows you down
Front-office staff move between several applications while the resident or client is kept waiting.
What we propose
An assistant that prepares draft replies and brings up the relevant background, while your staff remain in charge.
What you gain
Staff spend their time talking to people instead of searching.
Where a person decides
No reply leaves without a person sending it, and sensitive matters are passed on automatically.
Read about service assistance
04

Legacy modernisation

Illustrative workflowModernising one part at a time
All requests go through a fixed interface that sits in front of the old system.Functions move to new services one at a time; both outputs are compared side by side, and the team approves before the switch.
What slows you down
An old system carries rules and data you cannot do without, so any change feels like a gamble.
What we propose
A gradual replacement behind interfaces that do not change, so functions move to new software one at a time instead of all at once.
What you gain
Changes carry less risk, and your staff can keep improving the system.
Where a person decides
Each new part runs alongside the old system until your team approves the switch.
Read about legacy modernisation

04 Government & public entities

Built to stand up to public scrutiny.

600+public-sector projects across the EU, completed or still running, for ministries, agencies and public entities.

Ministries, departments and public entities need technology that everyone can use, that is secure and open to inspection, and that outlives the contract it was bought under. Over many projects we have learnt to work with public procurement rules, services in more than one official language and strict data protection.

AI gets the same care from us: recorded decisions, a person who can step in, and a design that takes account of the AI Act from day one. In Malta that means the authorities designated in 2025, with the Malta Digital Innovation Authority (MDIA) in the lead.

  • EU Member States
  • Other European countries
  • Offices
Government & public entities

Dot map of Europe with the 27 EU Member States, Malta among them, highlighted. Other European countries appear in a lighter tone, and the offices in Antwerp and Ghent are marked.

What a public entity can count on

  • Interoperability Open standards and interfaces that hold, in line with the Interoperable Europe Act and the principle that citizens give their data only once.
  • Accessibility Online services built and tested to WCAG 2.2 AA and EN 301 549, with S.L. 418.03 on public-sector websites and apps in view.
  • Sovereignty Data kept within the EU, hosting locations agreed with you in advance and no lock-in to one vendor.
  • AI Act readiness From risk classification to documentation and human oversight, prepared for review by the MDIA.
  • Procurement Documentation and decision records that support a tender submission on ePPS, an audit and an orderly handover.

05 Enterprise platforms

AI inside the platforms you already use.

Your client, finance, supply and operational records are already held in Salesforce, SAP or Odoo. We implement these platforms, extend them and link them to your other systems, then connect AI to them with the correct access rights, so automation runs within the processes your staff already follow.

  • Salesforce

    Summit Partner

    What we do

    • Set-up for sales, client service and public-service processes
    • Links to ERP, data platforms and back-office systems
    • Custom development where configuration reaches its limit

    With AI

    Help with case handling, with draft replies that staff check before they go out

  • SAP

    Gold Partner

    What we do

    • Integration and extensions through APIs and side-by-side applications
    • Controlled access to data for reporting and AI
    • Modernisation around a core that stays stable

    With AI

    Documents read into SAP processes, with exceptions passed to staff

  • Odoo

    Gold Partner

    What we do

    • Set-up and configuration for growing companies, including family businesses
    • Custom modules
    • Links to online shops, finance and CRM

    With AI

    Back-office tasks automated on the data in Odoo

Salesforce, SAP and Odoo are trademarks of the companies that own them.

06 Engineering depth

Most of a useful AI feature is dependable software.

The model is just one part. Around it you need integrations, access rights, testing, approval points and day-to-day operation, and these decide whether the feature still holds on the first busy morning of the week. This is where AI projects either succeed or fail without anyone noticing at first.

A sample architecture, one layer at a time

Illustrative architecture, not a system of any client
  1. AI is worth only as much as the systems it can read and update. So we design the integrations first: field mapping, retries, protection against duplicates and errors that staff can actually see.

  2. The system fetches only what the person asking may see. Access rights are applied in the retrieval layer itself and are never left to the wording of a prompt.

  3. Answers and actions are checked against agreed criteria both before and after each release. Any action with real effects waits until a person approves it.

  4. Infrastructure as code, separate environments and tracking of quality, response time and cost, so the system can be operated, audited and improved once it is live.

Read the diagram as text

Six layers are shown. From the top: agents and workflows, with a point where a person approves before any consequential action; models and evaluation; data and retrieval; the integration layer; and the business systems that hold the records, for example CRM, ERP, case management and document libraries. Beneath them all sits a cloud platform with monitoring.

Access control runs down through all six layers, so identity, roles and audit trail apply at every step. A request comes in at the top and travels down each layer until it reaches the business systems.

There are four notes: integrations before prompts (integration layer and business systems); retrieval within access rights (data and retrieval, access control); testing and approval points (models and agents); run, not just installed (cloud platform and observability).

Our approach to architecture

07 Approach

From the first meeting to a system in daily use.

Four stages, and each one closes with something you can check and retain. Progress is visible to you at each step, and what we build belongs to you.

  1. 1. Understand

    We look at the business problem, the people concerned and the systems in place, and together we decide what to tackle first.

    OutputProblem definition

    • Map of processes and systems
    • Limits and risks
    • An agreed first use case
  2. 2. Design

    We select an architecture, fix how success will be measured and plan a first release that is small enough to go live.

    OutputArchitecture and success measures

    • Architecture and recorded decisions
    • Quality and evaluation criteria
    • Plan for the release
  3. 3. Build

    We deliver in short, tested steps that your staff can look at, try out and question.

    OutputTested implementation

    • Increments that work
    • Automated tests and evaluation runs
    • Documentation written along the way
  4. 4. Operate and improve

    We either hand the system over or run it ourselves, watch it in production and keep improving it with you.

    OutputHandover and operating plan

    • Runbooks and monitoring
    • Ownership and support arrangements
    • List of planned improvements

Whatever operation teaches us goes into the next round of understanding.

08 Trust and sovereignty

Governed, kept within the EU, with people deciding.

We treat responsible AI as engineering work rather than a policy on paper. Four layers of control surround every system we build, and at the centre sit your data and your decisions.

  • Sovereignty and data residency

    We plan for data kept within the EU and agree the hosting locations with you before building starts, with sovereign options where your obligations require them.

  • Security and ISO/IEC 27001

    Our information security management holds ISO/IEC 27001 certification. Least-privilege access, threat modelling and secure engineering are part of how we deliver, starting at the design stage.

  • Governance and AI Act readiness

    Risk classification, documentation, audit logs and decision records, prepared with the AI Act and the GDPR in view, so you can show the MDIA or the Information and Data Protection Commissioner (IDPC) who did what and why.

  • Human oversight

    Approval points, escalation routes and the power to overrule the system, wherever an automated decision has real effects on people.

Your data and decisions

Credentials

  • ISO/IEC 27001Certified information security management
    • Salesforce Summit Partner
    • SAP Gold Partner
    • Odoo Gold Partner

The systems we build are designed for the GDPR, the AI Act and the Maltese NIS2 Order.

Our approach to security and data

09 In Malta

FromNine in Malta

Malta has already put its EU digital laws into effect. The NIS2 Order (Legal Notice 71 of 2025) has applied since 23 January 2026, with the Critical Infrastructure Protection Department (CIP Department) as competent authority. The authorities for the AI Act were designated in 2025, with the MDIA in the lead and the IDPC for certain high-risk systems. Under DORA, banks, insurers and investment services firms answer to the Malta Financial Services Authority (MFSA), with the European Central Bank (ECB) for significant banks. We build systems that let you show compliance with these rules to the authority concerned.

We have no office in Malta. Our teams work from Antwerp, Ghent and Amsterdam, in the same time zone as you. With clients in Malta we work in English.

Our public-sector experience covers 600+ projects for public bodies in EU Member States, completed or still running, including in Malta. We know the setting in which the Maltese public administration builds: shared Government ICT through the Malta Information Technology Agency (MITA), Malta e-ID for secure login, servizz.gov as the single portal for online services, and Malta Diġitali as the national digital strategy for 2022 to 2027. Calls for tenders appear on ePPS under the Public Procurement Regulations (S.L. 601.03), and we answer each criterion of the call for tenders in turn. On contracts above EU thresholds, Government accepts e-invoices in EN 16931 over Peppol.

Working languages
English · Italian

How this could look in Malta

Illustrative example
  1. A permit application with Malta e-ID login

    A public entity still receives permit applications on paper and by email, and staff re-enter each one before they can assess it.

    What we would put in place
    An online application with Malta e-ID login, linked from servizz.gov, that checks the supporting documents on submission and passes a complete file to the case system.
    Where a person decides
    Officers of the entity take every decision on the application; the system only prepares and checks the file.
    How we would track success
    Share of applications submitted online, number of files returned as incomplete, time from submission to decision.
  2. AI Act records kept as part of delivery

    A ministry introduces an AI assistant in several departments and has to be able to explain to the MDIA how it works, how it was tested and who answers for it.

    What we would put in place
    The delivery pipeline produces the technical documentation, test records and event logs itself, and stores them with each release.
    Where a person decides
    A named officer approves each release, and every logged decision can be examined and contested.
    How we would track success
    Documentation complete per release, time needed to answer an audit question, test results over time.
  3. Ready for the NIS2 Order

    A company in scope of the NIS2 Order has to register with the CIP Department and show its customers how its suppliers and incidents are managed.

    What we would put in place
    One workflow that records each incident once, keeps the supplier evidence in one place and prepares the notification that the company files.
    Where a person decides
    The security officer checks and files every notification; nothing is submitted without a person.
    How we would track success
    Time from detection to first notification, completeness of incident records, supplier evidence up to date.

Careers

2,400+ colleagues, and a place for you.

Engineers, architects, consultants and specialists who build AI systems, enterprise software and cloud platforms for Government and private companies in EU Member States. You work on problems that real users feel, next to colleagues who take pride in getting the details right.

  • Our hub for innovation and development is in Ghent.
  • Other teams work from Antwerp and Amsterdam.

Practices

  • AI engineering
  • Software engineering
  • Cloud and platform
  • Salesforce
  • SAP
  • Odoo
Two FromNine engineers working out a solution side by side

Roles in our teams

  • AI engineer
  • Machine learning engineer
  • Data engineer
  • Cloud platform engineer
  • Integration developer
  • Solution architect
  • Salesforce developer
  • SAP consultant
  • Odoo developer
  • Full-stack engineer
  • Test automation engineer
  • Delivery lead
  • Business analyst

Let us work out your next step.

In a first conversation we talk about the problem you want to solve, the systems you have and the most useful thing to do next. You do not need to prepare a presentation.

  • What you want to achieve and your limits
  • The systems you run today
  • A realistic next step

One team answers for the whole programme, in English, from Antwerp, Ghent and Amsterdam.