Lugbox is an AI box that sits in your office. Once you've added the meeting records and internal documents you choose, colleagues type questions in Cantonese and get back the relevant records and documents, with sources; if nothing is found, it says so. Lugbox's knowledge base and query AI run on a machine in your office; storage and search never go through LUGJI servers.
We're starting the pilot with organisations like these: lots of meetings, lots of documents, high privacy expectations — data that can't just be put in the cloud.
After the pilot, colleagues can ask“How did we finally decide on the venue and insurance for last year's sports day?”
After the pilot, colleagues can ask“What follow-ups came out of our last meeting with this client?”
After the pilot, colleagues can ask“What price and delivery date did we agree with this supplier last time?”
The knowledge base and queries stay in your office. Meeting organising uses cloud AI: the text passes through our relay server in Hong Kong (the relay stores no content) to Google Vertex AI; under Google's enterprise terms, your data isn't used to train AI models.
During the pilot, we provide all of the following.
Each step has something concrete to get done, and something we need from your organisation. Either side can stop at any time during the pilot. The pilot is currently open to Hong Kong organisations only.
We install the box on site and choose a first set of meeting records and documents with you as pilot data.
Data goes into the knowledge base, and we set which scope each colleague can see.
During the pilot, we go through the query log with you on the machine in your office, noting which answers worked and which didn't. The log stays on the machine and isn't sent out. Administrator accounts can see every colleague's queries.
We look at the results together and what needs changing. You decide whether to continue or stop.
This is how Lugbox is designed today.
Lugbox's knowledge base and query AI run on a machine in your office; storage and search never go through LUGJI servers.
Two ways in: documents your colleagues switch to “Add to on-device AI search” in Lugoffice (Lugbox licence required), which are removed from the knowledge base when the tag is removed; and existing company files that an administrator uploads to a designated knowledge base, which an administrator removes. Regular colleagues can't upload files themselves.
Each colleague has an account, created and scoped by your administrator. Documents without a scope aren't indexed — better left out than filed in the wrong place.
Colleagues type questions the way they'd normally say them in Cantonese. Answers list their source documents so you can check.
The pilot doesn't turn into a paid contract automatically. After the review, it's your call.
The machine belongs to your organisation, with a yearly care and support contract. Suits organisations with a capital budget.
We take the machine back, erase all the data on it, and give you proof of erasure.
The pilot machine suits a small team of about 1–5 people. If several people ask at once, their questions queue; an answer usually takes around half a minute.
One power socket (a UPS is recommended), a wired connection to your office network and a fixed internal IP address. Colleagues' devices need to be on the same internal network, with Wi-Fi client isolation turned off. No ports need to be opened to the internet; we'll give your IT team the internal ports before installation.
We recommend a locked or access-controlled location.
We agree this together before we start. For example: questions your documents can answer are answered correctly with the right sources; questions with no answer get a plain “not found”; permission tests pass.
Lugoffice documents stay on your colleagues' devices and in their iCloud. Lugbox doesn't keep the original files an administrator uploads, so keep your own copies.
30 minutes, on site or online. You tell us how your organisation holds meetings and keeps documents; we tell you where Lugbox can help — and where it can't.
Lugbox