What are you building?
What are you building?
Built for traffic and time
Members & CommunitySocial EntertainmentDigital EducationMember App DevelopmentMember cards, points and coupons, synced with POSBooking & Registration SystemsOnline booking, scheduling, check-in and eventsIn government system projects, the hard part is rarely the code. It is whether the requirements spec is clear enough, how security requirements are met, and what proves the work is done at acceptance. JoinX takes on systems such as case management, booking and registration, data platforms, IoT monitoring and AI adoption, builds them to the spec, security and acceptance requirements in the tender documents, and supports and extends them with the same team after launch.
Free requirements review · Reply within 1 business day · NDA available
JoinX experience
JoinX takes on system projects: case management, booking and registration, data platforms, IoT monitoring, and bringing AI into existing workflows. These projects need process, permissions, data and security designed together, and they are the main type of work JoinX does. We do not take on brochure websites, outsourced website builds, or annual small-scale maintenance with no development work. Every engagement follows the agency's procurement procedure and tender documents. Our public sector systems include Taipei's Cooc school cloud for the Taipei City Education Bureau, AI analysis of eddy current signals for the National Atomic Research Institute, and an online course live streaming platform for ITRI.
Real projects Public sector systems we have built
These are public sector and research institute projects that have been made public.
Taipei City Education Bureau
One entry point for 9 sub-systems, with different access for the bureau, schools, teachers, students and parents; vulnerability scans, version control and access control to the bureau's ISMS standard, plus support and incident reporting from 5×8 up to 7×12.
2022–2025National Atomic Research Institute (NARI)
Commissioned to develop an AI-assisted inspection system that identifies defects in eddy current signals from nuclear power plant equipment. Built in stages, from single-channel to multi-channel, with AI recognition and automation as two separate systems to reduce risk.
ITRI (Industrial Technology Research Institute)
An online course live streaming platform built for ITRI.
* Cases describe only the project scope that has been made public.
What we build Systems we take on
These are the public sector systems JoinX takes on. Brochure websites, outsourced website builds and annual small-scale maintenance are outside our scope.
Intake, assignment, review, requests for more documents, closure and history, with permissions and notifications by role for case officers, supervisors and citizens.
Bookings and registrations for venues, courses, events and services, with capacity limits, waiting lists, check-in and notifications.
Bring together data spread across units or systems, with search, statistical reports and data exchange interfaces.
Sensor and device data upload, real-time monitoring, anomaly alerts and history lookup.
AI inside existing workflows, such as image or signal analysis and document handling; validate on a small scope first, then expand based on results.
Take over an existing system, add sub-systems on the same platform, and handle monitoring, incidents and improvements after launch.
Which one Is it a fit
Our strength is system projects where process, permissions, data and security must be designed together. Here is what we take on and what we do not.
| Project type | JoinX | Notes |
|---|---|---|
| Case management, booking, data platforms and similar systems | We take these on | Process, permissions, data and security designed together; this is our main type of work |
| IoT monitoring and AI adoption | We take these on | We recommend a small validation or a first phase, then expanding based on results |
| Extending and supporting an existing system | We take these on | Projects centered on new features that also include support, such as Cooc's extension and maintenance contract |
| Brochure websites and outsourced website builds | We do not take these on | Public sector website projects centered on page content and layout are not something we currently take on |
| Annual small-scale maintenance | We do not take these on | Projects with only annual small-scale maintenance and no development work are not something we currently take on |
Process How we work
The process for a public sector system follows the agency's procurement procedure and tender documents. This is what we do at each stage.
Before tendering
When an agency publicly invites reference material under its procedure, we can provide information on technical approaches and development scope. Requirements are best written around the functions and outcomes needed, without unnecessary technical specifications.
Per the tender documents
We prepare the service proposal and presentation to the tender documents and evaluation criteria, setting out system boundaries, division of work, schedule, security approach and acceptance method.
Per the contract schedule
Permissions, personal data and activity logs are planned to the protection level required. Before delivery, JoinX runs its own source code and vulnerability scans (white-box); black-box testing is done by a third party, and JoinX can help arrange it and recommend a vendor, then fixes the findings before delivery.
Ongoing after launch
Each requirement becomes test scenarios and acceptance items, and test reports and documents are delivered per the contract; after launch, the same team supports and extends the system.
Pricing Budget reference
The amount for a government project is set by the agency's budget and tender documents. These are reference ranges for custom projects in Taiwan in 2026, for comparison when planning a budget.
| Scope | Reference range | Typical content | Timeline |
|---|---|---|---|
| Requirements and spec advice | NT$100k–300k | Interviews on the workflow, organizing functions, role permissions, data and acceptance items | 2–4 weeks |
| Small system or features for an existing system | From NT$150k | One more process, report or data integration on an existing system | Depends on scope |
| Single-process system | NT$500k–1M | The full process for one operation, such as case management or booking and registration | 3–5 months |
| Multi-role platform, IoT or AI system | Priced by scope | Several sub-systems, data across units, device integration or AI models, launched in phases | Phased |
IoT devices, cloud hosting, SMS and other third-party services are billed separately; third-party black-box testing follows the tender documents.
FAQ Common questions
System projects: case management, booking and registration, data platforms, IoT monitoring and AI adoption, plus extension and support contracts for existing systems that center on new development. We do not take on brochure websites, outsourced website builds, or annual small-scale maintenance with no development work.
Yes. When requirements are still unclear, an agency may publicly invite vendors to provide reference material under Article 34, Paragraph 1 of the Government Procurement Act, and we can provide information on technical approaches and development scope under the procedure the agency adopts. Requirements are best written around the functions and outcomes needed, without unnecessary technical specifications that could unduly restrict competition. The actual procedure still follows the case and the agency's procurement authority.
Under the Cyber Security Management Act and the Regulations Governing the Classification of Cyber Security Responsibility Levels, systems an agency develops itself or outsources must complete protection requirement classification and apply the corresponding controls, so permissions, personal data and activity logs are planned during requirements and architecture. Before delivery, JoinX runs its own source code and vulnerability scans (white-box); black-box testing is done by a third party, and JoinX can help arrange it and recommend a vendor, then fixes the findings before delivery. On Cooc, for example, vulnerability scans, version control and access control follow the education bureau's ISMS standard.
Start during requirements. Write each important requirement as a scenario someone can carry out, such as application, review and requests for more documents through to closure, then turn it into test cases and acceptance items. Test plans, test reports and deliverables follow the tender documents and contract; when requirements change, scope, schedule and acceptance criteria are adjusted together and recorded.
Three have been made public: Cooc, Taipei's school cloud and parent–teacher–student platform for the Taipei City Education Bureau (one entry point for 9 sub-systems, with ongoing extension and support); AI eddy current signal analysis and automation for the National Atomic Research Institute (developed in stages, 2022–2025); and an online course live streaming platform for ITRI.
The same team that built the system supports it, with no handover. On Cooc, for example, we set up support, monitoring and incident reporting from 5×8 up to 7×12, run regular backups and log audits, and handle the bureau's improvement and extension requests. Support scope and service hours are set by the tender documents and contract.
Related Related reading
Get started Start with the requirements
No full requirements specification needed. Tell us which operation you want to improve, who the users are, what data is involved, your expected procurement timeline, and your security and acceptance requirements. Any engagement follows the agency's procurement procedure.