Most companies still pay people to do work a machine should have finished overnight —
we take the busywork off the payroll, put agents on the workflow, and lock the door behind them.
02
Capabilities
Three systems. One operating discipline.
An IT company that builds, integrates, and defends the systems a business actually runs on. Pick the one that matches your problem — it carries straight through to the brief.
01
Process automation
Problem
Work moves by copy‑paste. Handoffs rot in inboxes. Nobody can say where an order actually is.
What we install
Process mining on the real event log, then RPA and API‑level orchestration with retries, audit trail, and a human checkpoint where the money is.
Outcome
The process runs on a schedule instead of somebody’s memory. Exceptions surface. The rest clears itself.
Brief this →
02
AI agent implementation
Problem
A chatbot answers questions. It does not file the claim, reconcile the ledger, or chase the supplier.
What we install
Multi‑agent systems with real tools, scoped memory, and hard boundaries. An evaluation harness before production and LLM ops after it.
Outcome
Agents that take an action, log it, and hand back the exception. Reviewed output — not improvisation.
Brief this →
03
Cyber security solutions
Problem
Perimeters age. Credentials leak. Most breaches are boring, documented, and preventable.
What we install
Zero‑trust segmentation, identity hardening, detection engineering, and SOC enablement your own team can operate on a Tuesday.
Outcome
Fewer paths in, shorter dwell time, and a response runbook that has actually been rehearsed.
Brief this →
03
Agent bay
Four agents. Each one has a job and a leash.
We name them, scope them, and write down what they are not allowed to touch. Autonomy without a boundary is just an incident waiting for a date.
SENTINEL
Defense
Automates
Continuous control checks, log triage, anomaly escalation with context attached.
Boundary
Read‑only on production. Isolates a host only on named human approval.
OPERATOR
Execution
Automates
Multi‑step back‑office workflows across ERP, CRM, mail, and the four legacy screens nobody will replace.
Boundary
Scoped service accounts, per‑action audit trail, no schema writes.
No outbound network. Cites the source or withholds the answer.
RUNNER
Throughput
Automates
Queues, retries, scheduled batch, the 03:00 jobs nobody wants to own.
Boundary
Idempotent tasks only. Dead‑letters after three failures and wakes a human.
04
Engagement
Five moves, in order.
No discovery theatre. Each step ends in something you can inspect.
01
Discover
We sit with the people doing the work and read the event log, not the org chart. You get a map of where time actually goes.
02
Model the process
The workflow is written down as states, owners, and failure modes before a single line of automation exists.
03
Deploy agents
Narrow scope first, evaluated against real cases, shipped behind a switch you control.
04
Harden
Identity, segmentation, secrets, logging. The automation gets the same scrutiny as the perimeter around it.
05
Run
Monitoring, drift checks, and a named escalation path. Systems are kept, not launched and abandoned.
05
Selected work
Three scenarios.
Illustrative engagements drawn from the kind of systems we build. Client names and figures are withheld; the shapes are real.
Scenario · illustrative
Industrial ops
Three shifts, four plants, one spreadsheet holding the downtime log together. We instrumented the line events, replaced the manual reporting chain with a scheduled pipeline, and put ANALYST on shift handover summaries. Supervisors stopped reconstructing the night and started reading it.
Scenario · illustrative
SaaS operations
Onboarding and billing exceptions were eating a support team alive. OPERATOR now works the queue end to end — provisioning, dunning, credit notes — and escalates only what falls outside policy. The team reviews decisions instead of typing them.
Scenario · illustrative
Platform engineering
A platform team inherited flat network access and shared credentials from a decade of growth. We segmented it, moved every pipeline to short‑lived identity, wrote the detections, and rehearsed the response until the runbook was boring.
06
Studio
Built in Novi Sad. On purpose.
LightSoft Global is an IT company: software engineers, integration specialists, and security people under one roof. Serbia has been producing hard engineers for forty years and exporting most of them. We stayed. That gives us deep technical bench strength, full overlap with the European working day, and the discipline of a market where nobody pays for a slide deck.
We work in small senior teams and we stay on the tools. The people who scope the system are the people who build it — and the people who answer when it pages at night. Alongside automation, agents, and defense, we do the ordinary IT work that holds it together: custom software, systems integration, cloud, and the long‑term run.
LightSoft Global
Danila Kiša 20
21000 Novi Sad, Serbia
07
Contact
Start a conversation.
Tell us the process. We will answer from Novi Sad.
Location Novi Sad, Serbia
Address Danila Kiša 20, 21000
Hours 09:00 – 18:00 CET
Response One business day
Brief received.
It is in front of an engineer, not a queue. You will hear back within one business day, from Novi Sad.
