Skip to Content

Paramaribo · Suriname — Infrastructure, software & ERP

From the rack
to the ledger.

Most IT firms hand you off. The network people blame the software people; the software people blame the ERP vendor. We build all three layers ourselves — so when something breaks, there is exactly one number to call.

Own datacenter capacity Custom module development NL · EN · Sranan
The stack 3 layers · 1 partner
L3
ERP system solutions
Odoo · Accounting · Inventory · Fleet · HR
L2
Software applications
Portals · APIs · Integrations · Mobile
L1
Hardware & infrastructure
Network · Virtualization · VPS · VDS
99.9% Uptime SLA, managed VPS
< 4h Response, business hours
3 Layers under one roof
24/7 Monitoring & on-call

What we do

We build it from the ground up.

Each layer stands on its own — plenty of clients hire us for one. But the reason they stay is that the layers were designed to sit on each other.

L1

Hardware &
infrastructure

The metal, the wire,
and everything that
has to stay powered on.

Network design & build

Structured cabling, managed switching, routing, VLAN segmentation and enterprise Wi-Fi — surveyed, installed and documented.

Virtualization

Proxmox, VMware and Hyper-V clusters with high availability, live migration and tested restore paths.

VPS & VDS

Dedicated vCPU and NVMe storage on our own capacity. Snapshots, off-site backup, and root access if you want it.

Servers, storage & backup

Specified, supplied, racked and commissioned. RAID, NAS and SAN, with a backup plan we actually rehearse.

L2

Software
applications

Built for the way
your business already
works — not around it.

Custom business applications

The tool that doesn't exist off the shelf, because your process isn't off the shelf either.

Web platforms & customer portals

Self-service portals that cut the phone calls: quotes, orders, invoices and status, all behind one login.

Integration & APIs

We make the systems you already paid for talk to each other — banking, payroll, e-commerce, customs.

Mobile & field apps

Installable apps that keep working when the connection drops, then sync when it comes back.

L3

ERP system
solutions

One source of truth
for finance, stock
and people.

Odoo implementation

Scoped, configured and rolled out on Odoo 19 — accounting, inventory, sales, purchase, fleet, HR and payroll.

Version migration

Stuck on an old release? We move live databases forward — data, customisations and all — with a rehearsed cutover.

Custom module development

Where standard Odoo stops, we extend it: local tax rules, multi-currency, exchange-rate feeds, industry workflows.

Training & support

Your team gets taught the system, not handed a manual. Then a support line that knows your database by name.

Payroll

Wages, loonbelasting and AOV run inside your ERP — payslips out, journal entries posted, built for Suriname businesses.

Explore payroll
ChatRoom (WhatsApp)

WhatsApp Business inside Odoo: every conversation lands on the customer, can become a lead, and stays on record.

Explore ChatRoom
Why the stack matters

Your ERP runs on our infrastructure, integrated by our developers, on a network we commissioned. That is not upselling — it is the reason your go-live doesn't turn into a three-vendor argument about whose fault the latency is.

Selected work

What that looks like in practice.

Every project below names the layers it touched. Notice how few of them stayed on just one.

Retail & distribution · 2026
L1 L2 L3
14 → 19 Odoo versions,
one cutover

Five years of ERP, moved forward without starting over.

The problem

A live Odoo 14 database, five major versions behind, out of support, carrying years of custom code nobody wanted to touch. Every upgrade quote they had been given began with "start over".

What we built

A repeatable migration pipeline, run against a copy of production until the cutover was boring. Custom modules ported, views verified, stale records cleaned — then a dedicated instance of its own so it stopped competing for resources.

Where it landed

Live on Odoo 19 with history intact. No data loss, no re-implementation, no starting over — and the migration kit is reusable for the next client stuck on an old release.

Vehicle sales & rental · 2026
L1 L2 L3
3 → 1 Systems,
collapsed into one

Rentals, sales and instalments in a single ledger.

The problem

Vehicles for rent lived in one system, vehicles for sale in another, and the instalment plans lived in a spreadsheet. Nobody could answer what a single vehicle had actually earned.

What we built

One fleet application where a vehicle simply carries a usage type — rental or sale. Instalment sales run on Odoo's own payment terms rather than a bolt-on, so the accounting is native and the reporting is free.

Where it landed

One vehicle, one record, one ledger — from purchase through rental income to final instalment. The whole fleet reconciles against the accounts without a spreadsheet in sight.

Non-profit · 2026
L1 L2 L3
512 Paper records,
imported & verified

A 500-member congregation, off paper and onto a phone.

The problem

Membership on paper, attendance in notebooks, and pastoral care tracked in people's heads. Nothing was searchable and nothing was safe from a flood or a fire.

What we built

Member and attendance management on Odoo, a pastoral-care workflow, and an installable mobile app carrying a full two-translation Bible, reading plans, bookmarks, and a prayer-request form that routes straight into counselling.

Where it landed

512 records imported and verified against the originals. 62,204 verses available offline. The whole congregation reachable from one system, on the infrastructure we already run.

Hospitality · Dolphins Suriname · 2026
L1 L2 L3
Book → Bill Reservation to refund,
one system

A hotel that books, checks in and settles up in one system.

The problem

Reservations taken by phone and notebook. Deposits, folios, restaurant tabs and refunds each tracked apart, so nobody could see a guest's whole stay — or what it had actually earned.

What we built

A full property-management system on Odoo: an online booking portal with live availability and pay-now-or-at-the-hotel, front-desk folios with security deposits, room changes, restaurant, laundry and transport charges, damage assessment, refunds and automatic housekeeping tasks — every move posting straight into the accounts.

Where it landed

Guests book online in minutes; the desk runs check-in to checkout from one screen; every deposit, charge and refund lands in the ledger on its own. Reservation to refund, one system.

Education · NATIN-MBO · 2026
L1 L2 L3
Ground up An IT room,
cabling to switch

A technical school's IT room, built from bare walls up.

The problem

NATIN-MBO needed a room to teach IT in, but had an empty one: no structured cabling, no network, no rack, and nowhere to seat equipment safely.

What we built

The room itself, as infrastructure — structured cabling and containment, a managed network with VLAN segmentation, a rack with switching and power, and the workstations and servers to fill it. Surveyed, installed, labelled and documented.

Where it landed

A purpose-built IT room the school teaches in every day — socket to switch to cloud, commissioned and handed over with the documentation to run it. Pure L1: the floor the other two layers stand on.

How we work

Four steps, in this order, every time.

We don't quote before we've seen the site. The order matters — most of the failed projects we get called in to rescue skipped step one.

Step 01Week 1

Assess

We walk the building, read the network, and interview the people who actually use the system. You get findings, not a sales deck.

Step 02Week 2–3

Architect

A written design: topology, hardware, hosting, modules, integrations. Fixed scope, fixed price, no surprises at invoice time.

Step 03Phased

Implement

Built layer by layer, tested on a staging copy of your real data. The cutover is rehearsed before it is performed.

Step 04Ongoing

Operate

Monitoring, patching, backups and a support line. The people who built it are the people who answer it.

The ITWASUR promise

Future-proof IT solutions.

Infrastructure, software and ERP under one roof — so the thing you build today still runs the way you meant it to tomorrow. That is what future-proof means.

Start here

Tell us what's
not working.

A consult is a conversation, not a pitch. Describe the problem — a network that keeps dropping, software you've outgrown, an ERP that never went live — and we'll tell you honestly whether we're the right people to fix it.

Drop Odoo's own Form block here (Blocks → Inner content → Form) and point it at Contact Form. It arrives styled — the theme skins Odoo's inputs, so submissions land in CRM as leads instead of in a mailbox.

Open the contact page