Custom developmentBuilt for you

Secure software development in every custom project

Security is cheapest when it is designed in, not added later. Every system we build follows the same standard as our own products.

  • GDPR by design
  • 24/7 operation and support
  • A team of 5 in Sofia, EU

Already running in production at organisations in Bulgaria — names under NDA.

How we prove it →

What we design in from the start

Role-based access

Every user gets only what their role needs; administrator rights are kept to a minimum.

Audit logs

Important actions are logged, so you can see who did what and when.

Encryption

Data encrypted in transit and at rest; credentials stored encrypted.

GDPR

Personal data handled under the GDPR: purpose, retention and the rights of the people concerned considered in the design.

Separation in multi-tenant systems

In platforms used by many customers, each customer's data is kept separate.

On-premises where needed

Systems and AI models can run on your own infrastructure when data must not leave your building.

Operated and patched

When we run a system for you, it is patched, monitored, hardened and online — 24/7.

Security decisions to take early (general guidance)

  • Which data is personal or confidential, and who may see it?
  • Where may the data be stored and processed: EU, your own servers, a specific provider?
  • How do users log in, and how are accounts removed when people leave?
  • How long is each kind of data kept?
  • What must be logged for audits?
  • What happens if the system is unavailable — how fast must it be back?

What to ask any development partner

General guidance for every partner, including us:

  • Who owns the source code and the data at the end of the project?
  • How are secrets such as passwords and keys handled in the code and in operation?
  • How are dependencies and security updates kept up to date after launch?
  • How are backups made and how is restoring tested?
  • Who has access to production systems, and is that access logged?
  • How will you be told about a security incident?

AI-specific security

When AI is connected to your systems, it must have only the permissions it needs, its actions must be logged, and it must be possible to switch it off without breaking the rest. That is what we mean by safe and reversible AI integration.

Security after launch

A system that was secure on launch day does not stay secure by itself. Updates must be applied, access reviewed and logs watched. When we operate a system for you, this is part of the job.

Contracts, ownership and disclosure

AI Fortis is a registered EU company. NDAs and data processing agreements are standard, contracts are clear, and ownership of the deliverables is agreed in writing before the work starts. The specific security measures and responsibilities for your project are part of that contract. If anyone finds a vulnerability in a system we built, we ask them to report it to us and give us a reasonable opportunity to fix it before any public disclosure.

Operations that stay secure

  • Production systems are monitored, patched and load-tested.
  • Administrative access is restricted, logged and auditable.
  • Secrets and credentials are kept in encrypted storage, never in plain text.
  • Access follows the principle of least privilege.
Free, no commitment

Request the security pack

Send us your security questions or your questionnaire. An engineer answers in writing for your deployment: architecture, data flows, access control, logging and GDPR processing.

  • Written answers from an engineer
  • Data flows and where the data is stored
  • Access control, audit logs and GDPR details

Your details are used only to answer this request.

Frequently asked questions

Is security included or an extra?

Included. Access by role, audit logs, encryption and GDPR are designed into every system we build.

Can the system run on our own servers?

Yes, where your requirements call for it — including AI models that run on your own infrastructure.

What does 'reversible' AI integration mean?

The AI gets only the permissions it needs, its actions are logged, and it can be switched off without breaking your other systems.

Who owns the code you write for us?

Ownership of code and data is agreed in the contract before the project starts. Ask us about the terms for your project.

Do you sign NDAs before we share details?

Yes. NDAs and data processing agreements are standard in our client work.

Who you are dealing with

A registered EU company and the people who wrote the code

Company
AI Fortis Ltd.
„ЕЙ АЙ Фортис“ ООД
EIK
208238799
Seat
Sofia, Bulgaria, EU
Team
Kristian Kamenov, Bojidar Komarov, Martin Paskalev, Vladi Avramov, Mariela
  • Named peopleYou talk to the engineers who built the product, not to a call script.
  • Proper paperworkContracts, NDAs and data-processing agreements as standard.
  • Clear pricing logicWe explain what drives the price before you sign, and confirm it in writing.
  • Your data, your rulesGDPR processes in every product. On-premises where data must stay inside.

What happens after you book

  1. You send the requestName and work e-mail are enough.
  2. We reply personallyWithin one business day, with times for a call.
  3. Short callWe look at your case and answer your questions.
  4. Written proposalWhat is included, what it costs, when it starts.

Ask about Custom development

Talk to us about the security requirements of your project.

  • GDPR by design
  • 24/7 operation and support
  • A team of 5 in Sofia, EU

Already running in production at organisations in Bulgaria — names under NDA.

How we prove it →