AITEH
RO

AITEH NexFlowCustom software

Software built around your process, delivered without surprises

AITEH NexFlow is AITEH’s custom software service: web applications, integrations and APIs built around your process. It is for companies whose processes do not fit an off-the-shelf product. Every release goes through separate environments (DEV, QAS, PROD) and automated security checks. We work in stages, with a fixed price for each stage, set in the proposal.

01.What we build

Applications that follow your process, not the other way around

When your processes do not fit an off-the-shelf product, we build software around them. We can start from scratch or take over an existing project.

Custom web applications

Screens and workflows designed around the way your team works.

Integrations and APIs

We connect the tools you already use, so data no longer has to be copied by hand.

CI/CD and DevOps on Azure

Safe, traceable delivery pipelines, from commit to production.

Maintenance and support

We stay involved after launch, with updates and support.

02.What we are doing now

NexFlow log

A short record of what we have been working on and what changed for our clients.

  1. Delivery across three environments: DEV, QAS and PROD

    We reorganised application delivery across three environments (DEV, QAS, PROD): separate CI and CD for each, deployments that only start after their own environment's build, and approval for production. The application reaches the server already built, so deployment no longer installs anything. Linting (with SonarSource rules run locally), tests and the security audit run in parallel, and if they find anything, the release stops for a single go/no-go review with every issue in one place.

    • Separate CI and CD for DEV, QAS and PROD
    • Deployments only start after their environment's build
    • Mandatory approval for production
    • The application reaches the server already built
    • Linting (SonarSource rules), tests and security audit in parallel
    • A single go/no-go review with every issue in one place

The path of a release

DEV

Development: every new change lands here first.

QAS

Quality assurance: we verify before clients see it.

PROD

Production: only starts with approval.

  1. 01

    Build (CI)

    Each environment has its own build. The application comes out ready to run.

  2. 02

    Parallel checks

    Linting with SonarSource rules, automated tests and a dependency audit.

  3. 03

    Go / no-go

    If anything is found, the release stops. Every issue, in a single review.

  4. 04

    Deploy (CD)

    Only starts after its environment's build. In production, only after approval.

03.Cybersecurity

Security is part of delivery, not a final step

We do not rely on “it works on my machine”. Every change goes through the same automated controls, and production is protected by explicit approvals. No accidental deployments, and no checks that “pass” without running.

Separate environments

DEV, QAS and PROD are isolated, each with its own CI and CD. Untested code does not reach production.

Production approval

No deployment to PROD without explicit human approval. You always know who approved it and when.

Pre-built releases

The server receives the application already built and installs nothing during deployment. What runs in production is exactly what we checked.

Static code analysis

Linting with SonarSource rules, run locally and in the pipeline, catches bugs and vulnerable code patterns before review.

Dependency audit

Third-party libraries are automatically checked for known vulnerabilities on every build.

Automated tests

Tests run on every change, so fixing one thing does not break another.

Go/no-go review

If a check finds something, the release stops. Every issue is in one place, for one decision.

Checks that actually run

A step that does not run is never treated as “passed”. The pipeline stops instead of skipping it.

Private networking on Azure

Where the project requires it, Azure services communicate through Private Endpoints on a private network, not over the public internet.

Two-factor authentication

2FA with TOTP (authenticator app) and token-based authentication through Laravel Sanctum.

Role-based access

Each user only sees and does what their role allows, including in SAP integrations.

Infrastructure as code

With Terraform, infrastructure is defined in code, versioned in Git and reviewed like any other change.

04.Technology

We work with

We choose the technology to fit the project, not the other way around. These are the tools we use every day.

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • Material UI
  • Angular
  • Laravel
  • PHP
  • Node.js
  • .NET
  • Payload CMS
  • MySQL
  • MariaDB
  • PostgreSQL
  • Redis
  • Docker
  • Nginx
  • Linux
  • Terraform
  • Git
  • WordPress
  • Elementor
  • WooCommerce
  • Shopify
  • XenForo
  • Stripe
  • SAP
  • PhpStorm
  • WebStorm
  • GitHub Copilot
  • Claude

Frontend

  • React 19, Next.js 15, TypeScript
  • Tailwind CSS, shadcn/ui, Material UI
  • Angularin our portfolio
  • Tiptap / ProseMirrorWYSIWYG editor for CMS

Backend

  • Laravel 12 / PHP 8.4with Sanctum (authentication), Queue Workers and Reverb (real-time WebSocket), in BizAITEH
  • Node.js with TypeORMCMS for a European sugar producer's multi-site platform
  • .NETin our portfolio
  • Payload CMSunder evaluation for Next.js websites

Databases and cache

  • MySQL / MariaDB, PostgreSQL
  • Redis
  • InterBasefiscal compliance in Bulgaria

Infrastructure and DevOps

  • Dockerseparate production and UAT stacks
  • Nginx, Linux, Windows Server
  • AzureApp Service, Blob Storage, Private Endpoints, API Management, Azure DevOps
  • Terraforminfrastructure as code
  • Git

CMS and e-commerce

  • WordPress + Elementor Prowith custom CSS, for business websites
  • WooCommerce
  • ShopifyCheckout Extensibility, Cart Transform and Rollouts, for international brands
  • ReChargeShopify subscriptions

Integrations and APIs

  • Stripepayments
  • SmartBill APIinvoicing and stock
  • Twilio Voice + OpenAI Whispercall recording and transcription in BizAITEH
  • WhatsApp and email inboxin BizAITEH and in dedicated WhatsApp applications
  • SAProles and permissions
  • Datecs and Adeopos REST APIfiscal printers in Bulgaria, POS in Croatia
  • PhpSpreadsheetExcel imports (ADEVĂR)
  • 2FA with TOTP

Development and AI tools

  • PhpStorm / WebStorm, VS Code
  • GitHub Copilotmulti-agent system
  • Claude

Do you have a process that does not fit an off-the-shelf product?

Tell us how you work today. We will tell you honestly whether custom software is the answer and how we would deliver it safely.

Updated