ltech@core — production type help ↵
L-Tech / Software & Infrastructure

Systems that keep running after we leave.

The stack, one layer at a time

Nothing here is a guess.

Every layer is chosen once and used everywhere: the same database patterns, the same auth, the same deploy path. New projects start at the point where most teams are still deciding.

What we build

Three kinds of work, one way of working.

Most requests land in one of these. If yours doesn't, say so plainly and we'll tell you whether we're the right people.

~/systems 01

Business systems

The software your staff open every morning: stock, sales, invoices, salaries, permissions. Built around how the business already works.

  • Inventory and point of sale
  • Multi-currency accounting
  • Role-based access and audit trails
  • Printable invoices in Arabic and Kurdish
~/interfaces 02

Web and mobile

Customer-facing products that load fast, read right-to-left properly, and don't fall apart on a mid-range Android.

  • Company sites and portals
  • Ordering and delivery apps
  • Trilingual interfaces, full RTL
  • Offline-tolerant behaviour
~/operations 03

Servers and support

We run what we build. Provisioning, certificates, backups, monitoring, and a person who answers when something is wrong.

  • Server setup and hardening
  • Deployment pipelines
  • Backup and restore drills
  • Maintenance agreements
Systems we built

Systems already running in the field.

Clients

The people who open our software every morning.

> after handover
Partners

Who we build with.

How we work

Written by hand. Every line accounted for.

No copied templates, no code nobody on the team can explain. You get the repository, the server credentials, and documentation written for the person who takes over after us.

Move your cursor across the hand
Contact

Tell us what you need to see.

new-message — whatsapp
$ whois l-tech
office  
hours   
$ compose --to l-tech
Opens WhatsApp with the message filled in. Nothing is stored here.
WhatsApp
>
↑↓ move↵ openesc close