CBX = Code · Build · eXperience
Software that works
on day one
Plug in chat, push and logistics today. Hand us the systems that need designing.
Built by an architect who has designed public, finance and defense systems since 2005.
Code, Build, eXperience.
Consultation is free. Private posts are read by the person in charge only.
Consultation hours: weekdays 09:00 – 18:00 (KST)
Development services
If it does not exist, we build it
The person who designs it writes the code, and the person who builds it runs it. Hands do not change midway.
Public · finance · defense systems
Designed to the standards of demanding sectors. From requirements and architecture to build, acceptance and audit documents.
JavaSpringeGovFramePostgreSQLOracle
Web & app services
Turn an idea into a running service. User screens and the operator console together, deployed to production.
ReactNext.jsREST API
AI agent development environments
Agents wired to your tools and data with Claude and MCP. Designed around the people who use them, so the team actually works with them.
ClaudeMCPPython
Modernization & integration
Fix the system you run without stopping it. New features attach through APIs; data moves intact.
API integrationData migration
Cloud migration & automation
Move to AWS and Docker, with deployment automation and monitoring. When something breaks, the alert arrives first.
AWSDockerMSA
Operations & maintenance
The builders run it. Incidents and feature requests come through one channel to the same team, on monthly or yearly contracts.
StabilizationMonthly contract
Our solutions
Plug in and it runs
Three building blocks we built and use ourselves. They attach to a running service through API and SDK, without downtime.
Add-Chat
Real-time chat
Do not build chat yourself. Real-time 1:1 and group chat plus an operator console, attached in a few lines of code. It keeps working as users grow.
- Every device, HTML5 and JSON standards
- File transfer · read receipts · threaded replies
- Statistics dashboard and admin console included
Add-Push
Push messaging
Stop pulling developers in to send a push. Your staff pick the audience, schedule the send and read the results themselves.
- Image and video push, guest delivery
- Segments · schedules · A/B tests
- Delivery logs and usage analytics in real time
Add-Flow
Logistics TMS / OMS
Stop reconciling orders, dispatch and delivery in spreadsheets. See the whole flow from order intake to delivery and settlement, tuned to your site rules.
- OMS — intake · stock allocation · shipping · returns
- TMS — route planning · dispatch · live tracking · POD
- Standardized booking, dispatch and settlement
How we work
How a small team owns it end to end
Instead of adding people the way large vendors do, we cut the work with design and automation.
Design comes first
Documents before code. We write the screen list and data flow, then build.
Working screens every two weeks
You check real running screens, not documents. If the direction is off, we fix it at that step.
Common solutions over clever ones
Standards and conventions over tricks, so another developer can read it six months later.
The builders run it
We do not stop at handover. After launch the same team takes incidents and improvements.
Agents do the agent work
Repetitive work goes to Claude and MCP agents; people are kept for judgment. Our own development environment works this way.
Scope is fixed in writing
What is in and what is out is written before the quote. Out-of-scope requests are quoted for the next phase.
Process
From first contact to operations
Six steps. At the end of each one we decide together whether to move on.
- 01
Consultation
Post on the board or email us. A person replies. It is free.
- 02
Scope & quote
What is in and what is out, in writing, then a quote.
- 03
Design
Screen list, data structure and architecture fixed first.
- 04
Build & demo
Built in two-week increments, verified on working screens.
- 05
Acceptance & launch
Tested together, deployed to production, with operations docs.
- 06
Operations
A stabilization period, then monthly or yearly maintenance.
Before quoting we write the screen list and data flow together. Solutions and system builds alike are quoted after scope is fixed, and consultation and quotes are free.
FAQ
Before you hand it over
Can I ask before the plan is ready?
Yes. We define scope together.
If you can say who it is for and what it should do, that is enough. We lay out screens and data flow first.
Does it integrate with what we already run?
We attach without stopping your service.
You get API documentation and template code. Solutions plug in; modernization keeps your data in place.
Will it hold up as users grow?
Designed on MSA so it scales with you.
Event-driven architecture handles heavy traffic without lag.
Resources scale automatically under load (Auto-Scale).
Faults are detected and recovered automatically (Self-Healing).
How much is it?
There is no fixed price table. We quote after the scope is written.
Integration scope — which service, screens and data it attaches to
User scale — concurrent users and monthly active users
Customization — how much screens, rules and permissions are fitted
Operations — whether we run it after launch (monthly or yearly contract)
What about security?
One-way hashing for personal data, TLS for transport.
SHA-256 one-way hashing protects personal data; end-to-end TLS protects transport. Rate limiting blocks abnormal calls.
What do I keep when it is done?
A state another developer can take over.
Source code and design documents
An operator console and an operations guide
Code written the common way, easy to hand over
Start the conversation.
Consultation is free
Post on the inquiry board and the person in charge reads and replies. Private posts are available.
Consultation hours: weekdays 09:00 – 18:00 (KST)