Integration
Omni: connect to anything
Every context layer has the same problem. There are more systems than anyone can build connectors for, and the one holding your context is always the one nobody supports. Omni is the answer to that. If your organisation can reach the information, so can Laylight.
What Omni connects to
Not just APIs. Omni connects Laylight to the systems your organisation actually runs on, whatever shape they happen to be in:
- Applications with an API, documented or otherwise
- User interfaces with no API at all, where the only way in is the screen a person looks at
- Your internal databases, scoped to the tables you choose
- On-premise and internal-only systems that never touch the public internet
- Tools built in-house that no one outside your company has heard of
- Legacy systems that nobody has maintained in years
- File shares, spreadsheets and the documents holding context no product ever captured
The question is not whether a system is on a supported list. It is whether your organisation can reach the information. If it can, Laylight can be connected to it.
Authentication is not a blocker
Systems worth connecting are behind a login, which is precisely why they are worth connecting. Single sign-on, multi-factor authentication, API keys, OAuth and ordinary username and password logins are all supported. A login screen is not a reason we cannot reach a system.
Questions
- What if the system has no API?
- We can still connect to it. Omni is not limited to systems that publish an API. If a person can reach the information through a user interface, Laylight can reach it too.
- What if it sits behind a login?
- Authentication is not a blocker. Single sign-on, multi-factor authentication, API keys, OAuth, session tokens and username and password logins are all supported. Credentials are stored encrypted and scoped to the connection they belong to.
- What if it is internal only and not on the public internet?
- Internal systems are supported. Tools that never leave your network, on-premise deployments and applications reachable only through a VPN can all be connected.
- What if it is a database rather than an application?
- Databases are a first-class source. You can connect a production database directly and scope Laylight to the specific tables you want it to read.
- What if we built the tool ourselves?
- Internal and custom-built tools are exactly what Omni exists for. There is no requirement for a system to be a product anyone else uses, or for us to have heard of it.
- What if the system is old and barely maintained?
- Legacy systems can be connected. The systems holding the most valuable organisational context are frequently the oldest ones, which is why they are in scope rather than excluded.
- Does Laylight need write access?
- No. Connections are read-only for retrieval. Laylight does not post, send, modify or delete anything in a connected system as part of answering a question.
- How do we get a system connected?
- Tell us which one at [email protected]. Connector priority is set by what people actually ask for, so naming the system is the fastest way to move it up the list.
Availability
Laylight is pre-launch, and Omni is rolling out alongside the 96+ systems in our connector catalogue. If there is a specific system your context lives in, tell us which one at [email protected]. Join the waitlist for access, or see Security for how connected data is handled.