01
Custom software
Management systems, point of sale, clinical records, academies and back office, designed around how your team actually works.
- Your own data model
- Multi-tenant with real isolation
- API and reports from day one
Software engineering · La Paz, Bolivia
Software built around your operation. Not the other way round.
We design, integrate and operate systems that carry processes where a mistake costs money, time or credibility: revenue collection, weighing, healthcare, retail, industry and customer service. Open code, data and documentation that stay with your company.
- Source code and database under your control, with no proprietary licences
- Integration with the equipment, sensors and systems you already run
- Training and support in your language and your time zone
- 7
- departments running SISCAP
- Vías Bolivia · 2012–2018
- 5
- departments running SNCPD
- tolling and weighing
- 80
- months of continuous operation in road infrastructure
- national systems
- 100%
- open-source software on the platforms we deliver
- DS 3251 · open standards
What we do
Three ways to work with us
We do not sell a box: we solve the whole process, from discovery to operation and hand-over to your team.
02
Integrations & IoT
We connect equipment and sensors to a single monitoring platform: tolling, weighing, CCTV, energy, agriculture and industry.
- MQTT, Modbus, OPC-UA, ONVIF
- Offline buffering
- Real-time dashboards and alarms
03
AI & automation
WhatsApp support, back-office agents and analytics with verifiable attribution, running on your data and your infrastructure.
- Human hand-off with context
- Every answer traceable
- Evaluation before production
The difference
Why not a closed ERP
A packaged system does not cost you in licences: it costs you in the three things you never receive.
| Criterion | Packaged ERP | TYKUN |
|---|---|---|
| Ownership | Usage licence: the vendor owns the code | Source code, migrations and data in your repository |
| Integration | Modules and connectors from the catalogue | MQTT, Modbus, OPC-UA, ONVIF, RFID, scales and PLCs |
| Changes | Configuration; custom work is quoted separately | The process is modelled and delivered in increments |
| Exit | Export reports and start over | Assisted migration, with no vendor dependency |
| AI | An optional catalogue module | Automation over your own data |
| Compliance | Proprietary licences, limited auditability | Aligned with DS 3251 and open standards |
Method
How we work
01
Assessment
Two to three weeks to map the real process, the systems already in place and the risks nobody is measuring today. You get a document with scope, architecture and a budget per phase.
02
Architecture and prototype
Data model, integrations and one screen running on real data. The prototype exists to discuss decisions before investing in the full system.
03
Incremental delivery
Releases every two weeks, with automated tests and a demo in your own environment. What you see is what gets deployed.
04
Hand-over and operation
Documentation, role-based training, admin credentials and a support period. Operations stay with your team, not ours.
Our own work
Systems already running at national scale
I would rather show what we built and sustained, with its real status, than a wall of logos.
Challenge
An ageing toll revenue system, with manual per-department deployments and no central traceability of operations.
What we did
- Relational design and changes to the system source code
- Deployment across 7 departments and support for toll and weighing posts
Status and outcome
- Sustained national operation throughout the period
- Foundation for later centralised monitoring
Challenge
Each station reported in isolation: there was no national view and no standard integration with lane peripherals.
What we did
- Development of the tracking and monitoring system
- Deployment across 5 departments
- Integration of weight indicators, traffic lights, barriers and IP cameras
Status and outcome
- Centralised view of stations and weighings
- Integration protocol reused in later proposals
Challenge
Digital affiliates cannot prove which ad produced each sale; attribution is lost between the landing page and the network.
What we did
- Multi-tenant architecture with row-level isolation and an append-only ledger
- OIDC identity, opaque click identifier and signed server-to-server postback
Status and outcome
- Foundations deployed and verified with isolation tests
- Dashboard and landing editor under construction
Start with the process that costs you the most today
A two-week assessment is enough to know whether to build, integrate or simply tidy up what already exists.
We reply by email or WhatsApp during Bolivian business hours (GMT-4).