Umbra Penance

Engineers who build systems, and know how they break.

Umbra Penance is a UK engineering company that helps growing businesses remove manual work and replace fragile processes with reliable systems: workflow automation, custom software and AI integrations, all security-tested by the engineers who build them.

Two people sketching a process flow on a whiteboard

Leadership

You speak to the people doing the work.

No account managers, no hand-off to a junior team. The people on your first call are the people who design, build and test your system.

  • Adel Acheli, Founder · Engineering & Security

    Adel Acheli

    Founder · Engineering & Security

    ISO 27001 Lead Auditor (certified)

    Designs and builds the systems, then tests them the way an attacker would. Shipped multi-tenant SaaS, internal tools, AI features and production automations, and delivers penetration test reports for live systems.

  • Mehdi Belmihoub, Co-founder · Automation & Growth

    Mehdi Belmihoub

    Co-founder · Automation & Growth

    Builds the automation systems that run day-to-day operations, from lead handling and sales booking to contracts and reporting, and works with clients on the commercial goal behind them.

How we think

Four principles behind every project.

  • Understand the business problem first

    We start from the process, the people and the numbers, and choose the technology last.

  • Build like it has to keep running

    Error handling, monitoring and documentation are part of the job, because the system will be used on a bad day too.

  • Test like an attacker would

    Whatever we build, we try to break before anyone else does. Security is designed in, then verified.

  • Leave clients independent

    You own the code, accounts and documentation. We'd rather be kept because we're useful than because you're stuck.

How we work

Clear from the first call to handover.

  1. Discover

    A 20-minute call, then a closer look at the process, the tools and where time or money leaks. You get a written recommendation, even if it's "don't build this".

  2. Design

    Fixed scope and price before any build. Data flows, access rights and failure paths are agreed on paper first.

  3. Build

    Short cycles with working previews. You see the system running on real data early, not at the end.

  4. Test

    Functional testing, then a security review of what we built: permissions, secrets, inputs, integrations.

  5. Launch & improve

    Monitored go-live, documentation and handover. Optional support plan; you own the code and the accounts.

Talk it through with an engineer.

You describe the process, the tools and where it breaks. We tell you what we’d automate, build or test first, and roughly what it would take.

Prefer to write? Send a short message
  • Pick a time in the next step
  • Free, no obligation
  • 20 minutes on Google Meet