A TTLock Alternative for Lock Brands That Want to Own Their Product
TTLock, developed by Sciener, is a fast, low-cost way to put software on a lock: off-the-shelf boards, a shared app, a cloud API and an SDK. Manufacturers usually look for an alternative when they want their own app and customers, US-hosted data, security documentation a buyer will accept, Wi-Fi locks without a gateway, responsive support, or features TTLock won’t build.
KoreLock is a US-based platform that covers all ten platform layers and designs boards and firmware around your lock. Read the full comparison.
POWERING SMART LOCKS FOR LOCK MANUFACTURERS AND ACCESS CONTROL PLATFORMS

When TTLock is the right choice
We’ll say it plainly: for budget residential locks shipped at high volume, or short-term rental locks where a shared app is fine, TTLock is the lowest-cost and fastest option, as long as the lock is designed around one of their boards.
Its rental features are mature (timed PINs, one-time codes, eKeys) and it works with Alexa and Google Home through its gateway.
When manufacturers switch
How TTLock and KoreLock compare on the things that usually prompt a lock brand to look for an alternative.
What you need | TTLock | KoreLock |
|---|---|---|
Your own app and customers | End users are in the shared TTLock app | Fully white-label apps under your brand |
Hardware | Design the lock around an off-the-shelf TTLock board | A custom board designed around your lock, or a ready-made module |
Connectivity | Mostly Bluetooth locks that need TTLock gateway hardware for remote access, voice control and smart-home bridging. Wi-Fi models can't be controlled remotely while in power-saving mode. | BLE plus patented Wi-Fi direct to the cloud, with no gateway |
Data hosting | TTLock-operated cloud (China-based) | KoreLock-operated AWS (US); dedicated AWS IoT instance available |
Security you can show buyers | Varies by factory; no public security disclosures | Secure boot, signed OTA, EAL 6+ secure element, mTLS, SOC 2-compliant cloud; review documentation under NDA |
Commercial access control | Strong for rentals and residential | Account hierarchies for multifamily, hospitality, retail, SMB and enterprise |
Custom features | Roadmap outside your control | US engineering team builds features you request |
Platform coverage | Modules, firmware, cloud and a shared app (4 of 10 layers) | All 10, including reader hardware and factory QA |
Volume | High-volume commodity economics | Built for the long tail; viable at 5,000–50,000 units |
The gateway problem
Most TTLock locks are Bluetooth-only, so every connected feature (remote access, voice control, smart-home bridging) needs a TTLock gateway. That adds a second device to the bill of materials, a second SKU for the channel to stock and a second product for support to troubleshoot.
TTLock does offer Wi-Fi models, but integrators are told to turn off their power-saving mode for remote control to work, which trades battery life for connectivity.
KoreLock locks reach the cloud over existing Wi-Fi, using patented dynamic wake-up schedules that keep the radio asleep until needed. There’s no gateway to sell or support, and you don’t have to choose between battery life and remote access.
The security question
In March 2024, CERT/CC published VU#949046, covering eight CVEs across Sciener’s lock firmware, the Gateway G2 and the TTLock app, including encryption downgrade, non-unique AES keys and unauthenticated firmware updates. The advisory records that CERT/CC received no statement from the vendor.
Commercial buyers send security questionnaires. KoreLock publishes its security architecture and provides review documentation to partners under NDA.
TTLock API vs KoreLock API
TTLock offers a cloud API through the TTLock Open Platform. It works, but it’s built around TTLock’s shared app: your integration acts on locks that sit in end users’ TTLock accounts, and most remote commands go through a gateway. KoreLock’s cloud-to-cloud APIs run on accounts under your brand, and Wi-Fi locks need no gateway.
-
Getting access: TTLock requires registering an app on the TTLock Open Platform, and approval takes a few days. KoreLock sets up API access with your cloud account during onboarding.
-
Authentication: TTLock uses a client ID and secret plus the lock owner’s TTLock app login. KoreLock uses OAuth 2.0.
-
Whose accounts: TTLock locks live in end users’ TTLock app accounts, and the lock’s top administrator has to connect each one. KoreLock accounts sit under your brand, on your white-label apps.
-
Remote commands: TTLock’s Bluetooth locks must be paired to a gateway, with remote unlock turned on in the app. KoreLock’s Wi-Fi locks reach the cloud directly.
-
Integrations: KoreLock’s cloud-to-cloud APIs connect to PMS, access control and building systems, with partners including RemoteLock and Z9 Security.
-
Feature requests: TTLock’s roadmap is outside your control. KoreLock’s US engineering team builds the API features you need.
AI assistants, too. KoreLock also offers an MCP connector for Claude and ChatGPT, so admins can query and manage locks in plain language. Permissions are set per connection, and AI can’t unlock doors or delete locks.
Moving off TTLock
A switch usually keeps your mechanics and replaces the electronics and software. We design a PCBA for the existing housing, port the credential features your users rely on (timed PINs, one-time codes, mobile keys), and launch your branded app.
Typical timeline: about six months to production-ready, with about 75% of the effort in board design and prototyping and 25% in firmware.
Read more
-
TTLock vs. Tuya vs. KoreLock: the three platforms side by side
-
Full comparison report: every platform layer compared
-
White-label smart locks: launch a lock line under your own brand
-
Smart lock module and custom PCBA: two ways to connect your existing lock
Frequently asked questions
A platform. TTLock, developed by Sciener, is a software platform and module ecosystem. Hundreds of factories build TTLock-compatible hardware that runs on the shared TTLock app and cloud.
Most do, because most TTLock locks are Bluetooth-only. Their Wi-Fi models skip the gateway but can’t be controlled remotely in power-saving mode. KoreLock locks connect directly to existing Wi-Fi.
Yes. Permanent, temporary and algorithmic PINs work online and offline, alongside mobile keys, NFC and cards, and wallet credentials through our credential partners.
On KoreLock-operated AWS in the US, on SOC 2-compliant infrastructure, with a dedicated AWS IoT instance available.
Yes, through KoreLock’s cloud-to-cloud APIs.
Yes. The TTLock Open Platform is a cloud API that works with locks in TTLock app accounts. Remote commands to Bluetooth locks need a paired TTLock gateway.
Yes. KoreLock provides cloud-to-cloud APIs with OAuth 2.0 for PMS, access control and building systems, on accounts under your brand.








