Security at aPlanner
A short summary of how aPlanner handles fab data today, and what is on the roadmap. The full description is on the Security & Deployment page.
Data stays in the fab
On-premise or private cloud inside the fab network is the default for Korean fabs, with an air-gapped option. SaaS is offered on the AWS Seoul region for suppliers and SMEs.
Encryption
Data is encrypted in transit (TLS) and at rest in the MVP; key management follows the deployment model the fab chooses.
Access control
Role-based access control, single sign-on via SAML 2.0 / OIDC and an immutable audit log of every plan change.
People decide
AI recommends; a planner approves, edits or rejects. Write-back to MES / ERP is enabled only after sign-off.
Compliance roadmap
SOC 2 Type II planned for 2027–28, ISO 27001 for 2028, K-ISMS planned. No certification is claimed before it is earned.
Clean-room development
The MVP uses no employer code or data; it is built on public methods and synthetic fab data.
Questions about security?
Talk to the founder directly about deployment inside your fab network and the compliance roadmap.