This Week at BATI: Building JSP Web's Production Environment, Securing Source Code, and Reviewing a Cloud Pilot Plan

Every Friday, we share a roundup of what the PT BATI Mulia Sejahtera team worked on from Monday to Thursday. The week of 19–22 October 2026 again centered on JSP Web, BATI's web-based job shop production scheduling service. Last week we laid the groundwork; this week we started building the production environment, tightened security, and took a careful look at the plan for a cloud pilot. 

Monday: Starting to Build JSP Web's Production Environment

Until now, JSP Web has been developed and tested in a staging environment. On Monday, we started building a production environment on a new server located in Indonesia, separate from staging. This is the environment customers will use day to day.
 
The design follows JSP Web's multi-tenant SaaS model: each customer gets its own workspace and database with its own subdomain on jobshopplanner.com, secured with SSL certificates. We also wrote a production deployment guide so that every update is released with the same documented steps.
 
•         Production and staging are kept separate: staging is for testing new features, while production only receives stable releases.
 
•         We also prepared a test scenario for the Project Template feature, which saves a project as a template so that similar projects (such as mold making) can be recreated faster, complete with their process sequence and machines.
 

Monday–Tuesday: Securing Source Code and the Deployment Pipeline

For a software company, source code is a core asset. So before production goes live, we drew up a security checklist covering the code repositories, servers and the deployment management panel. The checklist has 26 items, and 21 of them were completed the same day, including every mandatory item.
 
Security also extends to work devices. On Tuesday, we documented a short guide for resolving an email client issue on an encrypted data drive, along with preventive steps, so anyone on the team can fix a similar problem quickly.
 
•         Two-factor authentication (2FA) was enabled on the accounts that manage code and servers.
 
•         Access was reviewed: repositories are confirmed private, only authorized people have access, and deployment keys are read-only.
 
•         Unnecessary entry points were closed, such as new-account registration on the management panel and old access tokens no longer in use.
 

Monday–Thursday: Reviewing the Plan for a JSP Web Cloud Pilot

 
Following up on last week's migration assessment, on Monday we received a Statement of Work for a proof of concept of JSP Web on cloud infrastructure in the Jakarta region. We summarized the document so its key points are easy to grasp: work phases, architecture, roles and timeline.
 
The proposed architecture is in line with BATI's own design: a container-based application behind a load balancer, a managed MySQL database, and layers for security, monitoring and backup. On Thursday, we carried out a follow-up review, checked the document against the written clarifications we had received, and drew up a list of follow-ups so that every agreement is clearly documented before the document is approved.
 
•         Clear division of roles: the service provider prepares the infrastructure, while the BATI team migrates and deploys the application itself.
 
•         The review was organized by topic (scope, duration, sizing, account ownership and administration), with a status and an owner for each follow-up item.
 
•         The principle is simple: every commitment should be written down and consistent before anything is signed.
 

Closing

Building a reliable SaaS service is not only about features; it also takes a stable environment, disciplined security and well-documented agreements with partners. This week we worked on all three at once. Look out for our next roundup next Friday.
 
Want a better-organized production schedule for your workshop or factory with JSP Web? Get in touch with the PT BATI Mulia Sejahtera team at batimulia.com.