Skip to content
TrinolIT
TrinolIT

Software & AI studio · Dhaka, Bangladesh

Software.AI.Systems.

TrinolIT designs and builds websites, business software and AI systems for companies that need them to work correctly — in English and Bangla, from first scope to production.

Start a Project Explore Our Work
  • ShippedNexora AI
  • In buildTrinol OS · Trinol Payment
  • PricingPublished up front
  • ReplyWithin one working day

Technologies and practices we work with

  • Scope and acceptance maps
  • Decision records
  • Bilingual UX
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • WebGL
  • FastAPI
  • Python
  • Node.js
  • REST APIs
  • Retrieval (Qdrant)
  • Tool whitelisting
  • Grounding checks
  • PyTorch
  • Forecasting
  • PostgreSQL
  • SQLAlchemy
  • Alembic migrations
  • Decimal money
  • Ledgers
  • Docker
  • Vercel
  • Domains and TLS
  • GitHub Actions CI
  • Playwright
  • Vitest
  • Reversible releases
  • Row-level security
  • MFA
  • Field encryption
  • Security headers
  • Audit trails
  • Structured logs
  • Web Vitals
  • Error capture

Selected work

Real products,shipped and in build.

One system delivered to a business, and two of our own products being built now. Each case study explains the problem, the architecture and what changed — with the method behind every figure.

Nexora AI: one sale at the till updates stock, cash, VAT and the ledger in a single transaction, then the assistant answers a question asked in Bangla from those same records.

Shipped · Retail and trading01 / 03

Nexora AI

One system for a retail or trading business — till, stock, suppliers, invoices and books — with an assistant that answers questions from your real numbers.

Problem
The till, the stock, the suppliers, the invoices and the books live in separate tools that someone has to reconcile by hand — so the numbers disagree.
Solution
One system with one login, where a sale updates stock, cash, VAT and the ledger at the same instant, and an assistant answers questions from the live records.
Outcome
Five tools replaced by one. A checkout is written completely or not at all, and the assistant cannot state a figure that is not in your records.
  1. Till and web app
  2. API
  3. Isolation
  4. Database
  5. AI copilot
  6. Audit
Trinol Payment in build: a mobile-wallet payment is observed by the Android companion, matched to its order, reserved and consumed once, a signed webhook confirms the order, and a second attempt to use the same transaction is refused.

In build · Payments02 / 03

Trinol Payment

Payment confirmation and reconciliation for businesses that take payments into personal mobile-wallet accounts — each payment matched to its order automatically, once and only once. Release candidate; live use awaits approvals.

Problem
A business receiving payments into a personal mobile-wallet (MFS) account has no gateway telling it which order a payment belongs to — so someone confirms each one by hand, and the same payment can be counted twice.
Solution
An authorised Android companion reports structured transaction facts. The platform matches each one to exactly one order, reserves and consumes it atomically, records it in an append-only ledger, and tells the merchant's store through a signed webhook.
Outcome
Release candidate. All eighteen planned phases are implemented and validated in tests; live ingestion stays off until provider policy, device distribution and physical-device tests are approved.
  1. Checkout
  2. Android companion
  3. Signed ingestion
  4. Matching
  5. Consume service
  6. Ledger and webhooks
Trinol OS in build: company modules in a sidebar, a task card moving across the Kanban board to done, and an invoice going from draft to sent to paid.

In build · Company operations03 / 03

Trinol OS

TrinolIT's own company operating system — projects, tasks, leads, clients, meetings and finance in one place. In build now, on the way to a product for agencies and SMEs.

Problem
A growing studio runs its projects, tasks, leads, clients, meetings and invoices across separate tools and spreadsheets, so nobody can see the whole company in one place.
Solution
One operating system for the company — projects with a Kanban board, a sales pipeline that converts leads into clients and projects, meetings whose action items become tasks, and finance with invoices and payments.
Outcome
In build. Four phases are closed after independent review and finance is underway. V1 is done when TrinolIT runs on it for four consecutive weeks without falling back to a spreadsheet.
  1. Web app
  2. Identity
  3. Sessions
  4. API
  5. Organisation scoping
  6. PostgreSQL

All work and case studies →

Services

What we build,by the outcome you need.

Seven services in three groups. Pick one to see what you get, what it is built with and what it starts at.

A website wireframe fills in with design, adapts to a phone screen, and receives a visitor’s enquiry.

Websites and products

Get found, look credible and turn visitors into enquiries.

Fast, responsive business websites with SEO built in — from a five-page starter to a fully custom, animated site.

Typical deliverables

  • Responsive pages designed for your content
  • Contact form and WhatsApp handoff
  • SEO: titles, descriptions, sitemap and structured data
  • Deployment with domain, certificates and analytics

Technology

  • Next.js
  • React
  • TypeScript
  • Structured data

Starting at

From ৳14,999

Explore websites

Philosophy

We build systemsthat have to be right.

Most software works on a good day. Ours is designed for the other days too — when two people edit the same record, a payment is retried, or a question has no answer in your data.

  • Reliability

    A checkout is one database transaction: every record is written, or none is.

  • Data integrity

    Money is stored as exact decimals, and posted accounting entries are corrected by reversal — never edited.

  • Secure architecture

    Each customer’s data is separated by independent layers, and a request for someone else’s record returns “not found”.

  • Measured AI

    The assistant chooses from permission-checked tools and cannot state a figure that is not in your records.

  • Observability

    Important changes leave an audit event, so you can see who changed what, and when.

  • Maintainability

    Typed code, reversible migrations and tests — in your repository from the first commit.

Inside TrinolIT

See how oursystems behave.

Pick a request and follow it through the stack — including what happens when something fails. Nothing is left half-finished.

A page served quickly, to the right person, with nothing leaking.

  1. 01Client
  2. 02Edge / API
  3. 03Auth
  4. 04Service
  5. 05Database
  6. 06Queue · AI · Cache
  7. 07Observability

Capability map

Depth acrossthe whole stack.

Nine areas we work across, each with the tools our work actually uses.

  • 01

    Product

    Turning a business problem into a written scope, acceptance rules and a phased plan.

    • Scope and acceptance maps
    • Decision records
    • Bilingual UX

  • 02

    Frontend

    Responsive, accessible interfaces that load fast on real phones.

    • Next.js
    • React
    • TypeScript
    • Tailwind CSS
    • WebGL

  • 03

    Backend

    Typed APIs where every request is checked before it touches data.

    • FastAPI
    • Python
    • Node.js
    • REST APIs

  • 04

    AI and ML

    Assistants grounded in your records, and models measured per class.

    • Retrieval (Qdrant)
    • Tool whitelisting
    • Grounding checks
    • PyTorch
    • Forecasting

  • 05

    Data

    Schemas where the database enforces the rules, not just the app.

    • PostgreSQL
    • SQLAlchemy
    • Alembic migrations
    • Decimal money
    • Ledgers

  • 06

    Infrastructure

    Deployments that are reproducible and handed over, never held hostage.

    • Docker
    • Vercel
    • Domains and TLS

  • 07

    DevOps

    Every change built and tested automatically before it ships.

    • GitHub Actions CI
    • Playwright
    • Vitest
    • Reversible releases

  • 08

    Security

    Isolation in independent layers, tested by suites built to break it.

    • Row-level security
    • MFA
    • Field encryption
    • Security headers

  • 09

    Observability

    Knowing what happened, who did it and when — before a customer tells you.

    • Audit trails
    • Structured logs
    • Web Vitals
    • Error capture

How we work

Seven stages.No surprises.

Every stage produces something you can inspect, ends with a decision you make, and can stop without losing the work so far.

  1. 01DiscoverWe learn how your business works today, who will use the system and what it has to get right.
    Outputs
    Notes on goals, users, constraints and budget
    Decision gate
    Is this worth building, and are we the right team for it?
    Your involvement
    A conversation with the people who know the problem.
    Done when
    Both sides agree on the problem and the budget range.
  2. 02DefineWe write the scope: what is in, what is out, and how we will know it works.
    Outputs
    Written scope, acceptance rules and a fixed price per phase
    Decision gate
    You approve the scope and price before any build starts.
    Your involvement
    Review and sign off the written scope.
    Done when
    The important success and failure cases are written in testable language.
  3. 03ArchitectDecisions that are expensive to reverse are recorded with their cost, not just their benefit.
    Outputs
    Architecture and decision records
    Decision gate
    Hard-to-undo choices are agreed in writing.
    Your involvement
    Review the key trade-offs, explained in plain language.
    Done when
    Each expensive decision lists its cost, alternative and rollback path.
  4. 04BuildProduction code from the first commit: typed, migrated and tested, in your repository rather than ours.
    Outputs
    A running slice of the product in your repository
    Decision gate
    The slice works against real infrastructure.
    Your involvement
    See working software at every phase — not slides.
    Done when
    The slice passes its agreed checks.
  5. 05ValidateThe paths that carry money, identity and permissions get tests designed to break them.
    Outputs
    Test evidence for the acceptance and failure cases
    Decision gate
    Nothing launches with a failing critical check.
    Your involvement
    Try it yourself against the acceptance rules.
    Done when
    Money, identity, permissions and concurrency survive the cases designed to break them.
  6. 06LaunchDeployment, documentation and a walkthrough with the people who will own it.
    Outputs
    Deployment, runbook and owner walkthrough
    Decision gate
    Your team can deploy and operate it.
    Your involvement
    A handover walkthrough with your team.
    Done when
    Your team can deploy, operate and change the system without TrinolIT.
  7. 07ImproveSupport after launch, then optional maintenance — monthly or task by task, with no required retainer.
    Outputs
    Fixes, improvements and a record of every change
    Decision gate
    Continue only while it is useful to you.
    Your involvement
    Tell us what to improve next.
    Done when
    Each change is tested and documented before release.

The full process, and how phases are billed →

Company

A small studioyou can check.

TrinolIT is a software and AI studio in Dhaka. Everything on this page is verifiable — and what we cannot verify, we do not claim.

The TrinolIT mark assembling: the badge draws, the T drops into place and the name appears.
About TrinolIT →Our proof standard →
Based
Dhaka, Bangladesh — working with clients across time zones
Languages
English and Bangla: interfaces, documents and mixed-script input
Ownership
Your code from the first commit, with no licence or hosting lock-in
Delivery
In phases, each with a written exit state; you can stop between phases and keep the work
Pricing
Published up front, with the scope written beside every figure
Track record
Nexora AI shipped; Trinol OS and Trinol Payment, our own products, in build

What we will not claim

  • Client counts without a client register
  • Ratings without a public review source
  • Accuracy scores without the dataset and method
  • Team size, offices or certifications we cannot verify
  • Case studies built from a capability rather than a delivered project

Start a project

Build somethingthat has to be right.

Tell us what you want to build and who will use it. You do not need a technical brief — a few sentences is enough to start.

  1. 01We read your briefA person replies within one working day, with any questions we need answered.
  2. 02We clarify on a callGoals, priorities and budget — so the proposal covers what matters.
  3. 03You get a written scopeScope, price per phase, timeline and ownership terms, before any work starts.
Or write directly
hello@trinolit.com
Where
Dhaka, Bangladesh
Optional — helps us reply usefully

We use these details only to reply to you. See the privacy policy.