Visibility first
Inventory, state and boundaries before automation. A clear “not connected” state is better than a confident guess.
SIMCAT is built around a simple belief: you should be able to see and control your own eUICC lab without a cloud account, a hidden write path or a marketing claim that outruns the evidence.
Inventory, state and boundaries before automation. A clear “not connected” state is better than a confident guess.
Read-only first, explicit writes, manual rollback. The safe path is the default path, not an advanced setting.
Hashes, manifests and test records. If a result is limited, say so in the same sentence as the result.
SIMCAT started as a way to make eUICC work on a desk less opaque: one place to see readers, profiles, routers and WiFi Calling experiments, with a local service that does not need a cloud account.
The product family now spans a Windows/Linux/OpenWrt desktop app, an Android companion and a router/CPE surface. iOS and macOS are reserved workspaces, not shipped products.
We separate built, tested, deployed and verified. A build that was not deployed is not a deployment. A single downlink is not two-way voice. A lab result is not a carrier-grade fix.
This is slower than a hype page. It is also the only way to make a lab tool trustworthy.
For product questions, integration work or security reports, use the contact page. Do not send private keys or activation codes.