A Knowledge Base You Can Trace
Every answer comes with its source document — not just text that sounds convincing.
Learn more- Year founded
- 2026Year founded
- Service pillars
- 0Service pillars
- From brief to prototype
- < 0 weeksFrom brief to prototype
- Source code owned by client
- 0%Source code owned by client
Tools
Technology we use.
n8nLangChainPythonJavaScriptTypeScriptReactVueNext.jsTailwind CSSNode.js
Approach
Not promises, this is what we build.
Five real snapshots of how we work — from a knowledge base to the lines of code left in your hands.
Agent Workflows That Run Themselves
Emails come in, attachments get read, data gets checked, reports get sent — without anyone watching each step.
Learn more
System Design That Matches How You Work
Database schema and API contracts are sketched while you're still in the room, not after weeks of silence.
Learn more
Interfaces That Don't Need a Manual
If someone has to call support to do something basic, the design has failed.
Learn more
Code You Can Actually Maintain
No hacks that break the next time a package updates. No comments saying 'don't touch this.'
Learn moreProjects & Innovation
Some of what we've already built.
Screenshots will be replaced with real work once available.
Why RekanTech
A partner who thinks with you.
Most vendors wait for a spec and build it exactly. We refuse that. If an assumption in the brief is wrong, we say so upfront — not after the budget is gone.
We stay small on purpose. The person who audits your problem is the person who writes the code, so no context is lost in hand-offs between divisions.
- Audit first, code later. We find the root cause before writing the first line.
- From brief to prototype in under two weeks. You see progress, not reports.
- Code, documentation, and infrastructure access are yours from day one.
Insight
What's new at RekanTech?
Notes from real work: what worked, what failed, and why.
AI Engineering · 2026年8月12日
RAG That Doesn't Hallucinate: It's Retrieval, Not The Model
Swapping models doesn't fix wrong answers. What decides it is how documents are chunked, tagged with metadata, and re-ranked.
8 min read
AI Automation · 2026年7月29日
Automation That Isn't Fragile: Design To Fail Cleanly
Every automation flow breaks someday. What separates good systems is retry queues, idempotency, and an audit trail a human can read.
6 min read
Software Development · 2026年7月4日
The Hidden Cost Of Microservices For Teams Under Ten
Splitting services moves complexity from code to the network. For small teams, a tidy monolith almost always wins.
7 min read
Mobile Development · 2026年6月18日
Designing Mobile Apps For Indonesia's Up-And-Down Networks
Offline-first isn't a luxury feature. Outside big cities, optimistic sync is the difference between an app used and an app abandoned.
5 min read
Services
Four pillars, one team.
Not four separate divisions. The people who design the system are the ones who maintain it after launch.
Capabilities
Eighteen things we actually do.
Not a keyword list. Every item has shipped to production and been maintained since.
RAG & Semantic Search
Search that understands intent, not keyword matches.
AIAgents & Tool Calling
Models that actually carry out the task.
AIEvaluation & Guardrails
Measure accuracy before anyone relies on it.
AITargeted Fine-Tuning
Retrain only when prompting has hit its ceiling.
AIComputer Vision
Read documents, field photos, and CCTV footage.
AISpeech & Transcription
Meetings and calls become searchable text.
AIDocument Automation
Invoices and contracts processed without manual entry.
AutomationCross-System Integration
ERP, CRM, and spreadsheets speaking one language.
AutomationWorking Principles
What you can hold us to.
No testimonials to show off yet. What we do have: the rules we hold to on every project.
Transparent From Day One
Scope, estimates, and progress stay open. Bad news is delivered while it's still cheap to fix, not at the end of the project.
Code And Docs Are Yours
Repository, runbooks, and infrastructure access are handed over in full. No vendor lock-in, no portal you have to keep paying for.
We Say No To Unneeded Features
If a feature doesn't solve the problem you brought us, we say so upfront, even if it shrinks the project's value.
Support After Launch
Launch isn't the finish line. There's a handover period so your team can truly run the system on its own.
Journey
Just getting started, and written honestly.
Scroll to see them all →