Why olee
Five products, and none of them is a bundle.
Each one stands alone
OleeVision, OleeHire, Oleon, OleeASK and OleeLaw each have their own sign-in and their own bill. You pay for the one you use, not for the others.
Your data stays yours
Each product runs its own database with row-level isolation between clients, and nothing you upload is used to train a model.
Answers you can check
Every field OleeVision reads carries a confidence score, so your team looks twice only where it matters.
Built here
Sinhala and Tamil where they matter, LKR on the invoice, and support in your timezone.
Getting started
Three steps, and none of them is a sales call.
You can be inside a product in the time it takes to read this page.
01
Pick the product
OleeVision reads your documents. OleeHire fills your open roles. Oleon answers your customers. OleeASK answers from your own documents. OleeLaw researches the law. Start with the job that is waiting.
02
Create your account
Sign up on the product itself with your work email. There is nothing to install.
03
Add your people
Invite colleagues and choose what each one may open.
Security
Isolation is enforced by the database, not by our good intentions.
Every product keeps its own Postgres database, and every table that holds client data carries a row-level security policy. An application bug is not enough to show one client another client's rows, the query has to get past the database as well, and it does not.
01Row-level isolation per client, in every product
02A bot check in front of every sign-in
03Nothing you upload is used to train a model
04Delete a document and what was read from it goes with it
05Every administrative change written to an audit log
Pick one, and have it running this week.
Documents read into clean fields, a shortlist instead of a pile, customers answered while you sleep, your own documents answering questions, or the case law found. Start with the one you need.