Main content

Services

An agent needs software around it. Both need to be secure.

FIG. 2Agent pipeline
AI agent pipeline for back-office automation: documents reach an agent that reads and checks them, a person approves each draft, and only approved entries reach the ledger.DraftApprovedDocumentsAgentReads, checksPersonApprovesLedger

Stack

  • Python
  • MCP
  • FastAPI
  • SQLite
  • Bash
  • Docker
FIG. 3System architecture
Custom software architecture: an IoT sensor talks to a mobile app, the app syncs to one database, and a web platform reads the same data.SensorAppWeb appDatabase

Stack

  • Next.js
  • React Native
  • Swift
  • Supabase
  • ESP32
  • TypeScript
FIG. 4From scope to evidence
NIS2 readiness as a flow: a scope check feeds a gap analysis matrix of the Article 21 measures; one cell is marked as a gap, which goes to the fix list and then to the evidence index.ScopeFix listEvidenceArticle 21 measuresGapFix, then evidence

Stack

  • OWASP
  • NIS2
  • ISO 27001
  • Cloudflare
  • Let's Encrypt
  • PostgreSQL

Work

What each project changed.

All case studies
LifeOS, two of its processes: a finished call goes to an agent that files the meeting note; invoices pass automatic checks, and a person approves every payment.Meeting notesMonthly financeCallAgentNoteInvoicesChecksPerson

Our own studioLifeOS

7min

from call to a filed meeting note

Instruments

Gauges from real projects, fed with demo data.

Meeting notes filedDemo data

9this month

LifeOSOur own back office
Visitors in the roomDemo data

15people

In
35
Out
20
Muzeul BaiaPeople counters
Early or lateDemo data

+0.47sLate

Regularity Rally SystemOwn R&D, prototype

Process

How a project runs.

FIG. 5One project, end to end
One custom software project drawn as a line: the process is mapped on paper, the scope agreed in writing, the build tested from day one, the launch rehearsed before the switch, and fixes shipped as small reviewed updates.MapThe process on paper firstScopeWhat gets built, in writingBuildTested from day oneLaunchRehearsed before the switchFixesSmall, reviewed updates

Security

What NIS2 asks for, built into the software we ship.

FIG. 6NIS2 measures, built in
NIS2 cybersecurity measures as we build them into business software.A staff app on a database with access by role and a record of changes; documents checked before anything is paid, with a person approving every payment.LoggedStaff appSecure sign-inDatabaseBy roleAudit trailInvoicesPDF, emailChecksBefore payingPayment fileA person approves

Every brief reaches the team that builds it.

One email is enough to start, in English, Romanian or French.

Studio
Cluj-Napoca, Romania, EU