MILabs
Tools

Onyx AI assistant setup for small business

How small businesses use Onyx, a self-hosted agent platform, and how MILabs sets it up on the owner's own infrastructure.

Updated 2026-03-05

What Onyx is

Onyx is a self-hosted agent platform. It is software a business installs on servers it controls, then uses to build and run AI assistants that work with the business's own information. Because it runs on the company's own infrastructure, the business decides where its documents and conversations are stored and who can reach them, rather than relying only on a service run by someone else. A small business often turns to a platform like this when the knowledge it needs sits across shared drives, email threads and the memories of a few long-serving staff, and it wants one place to ask questions. Setup takes more care than a hosted tool, since the business or its IT provider takes on updates, backups and access. Onyx suits businesses where that responsibility is manageable and where the data path matters. On its own the tool is neutral, and its value depends on the sources connected to it, the people who use it and the rules that govern what it may answer.

Onyx: official site

Onyx in plain language

An AI agent is a program that takes a request, works out a sequence of steps and carries them out. Some steps read information, some write it, and some pass a result to a person. The language model at its centre supplies wording and reasoning, but alone it only knows what it was trained on. A business question about its own pricing, forms or past jobs needs extra material, which is where a platform like this earns its place.

The usual approach is to gather a business's documents into a searchable index, then pull the most relevant passages when someone asks a question and pass them to the model. When this works well, the answer can point back to its source file, so a reader can check the claim rather than trust it. When it works poorly, the reply sounds confident while drawing on the wrong document, which is why source material matters as much as the software.

Self-hosting moves choices such as where the platform runs and how long logs are kept onto the owner. Those choices need a named person and a review date, which is worth settling before anything is built.

What businesses use it for

  • Answering staff questions from policies, procedures and past project notes
  • Finding the right clause, price list or template in shared folders
  • Onboarding new team members with a question and answer guide to internal material
  • Drafting first replies to client questions, checked by a person before sending
  • Searching internal records to prepare for compliance checks and audits

Who it suits

  • Businesses with a private document store they want to query without sending it to a hosted service
  • Teams with an in-house IT person or a provider who can run and update the server
  • Organisations in regulated fields such as legal, accounting or health that need control over where data is held

How MILabs sets it up

MILabs starts by agreeing with the owner or team lead which problem the assistant should solve and what information it may draw on. That decision shapes the plan. Together the team chooses the hosting arrangement and confirms who keeps the server running. Next, MILabs connects the systems the business already has, such as shared drives, document stores and daily staff tools, checking that each source is one the business is happy to expose. Permissions are set so people only see answers drawn from material they are already allowed to read. Finally, the owner and MILabs agree who looks after the platform after handover, covering updates, backups, access reviews and what happens when a source changes.

Builds it fits

Industries it fits

Onyx in practice

Inside a business that runs Onyx, the work tends to look less like installing software and more like keeping a shared body of knowledge accurate. A team member asks a question and the answer comes back with the passages it drew on. The useful habit is to read those passages as well as the reply. If a reply cites an out-of-date version of a form, the problem sits in the folder, so retire or relabel that file rather than rewording the question.

Most of the ongoing effort sits with a named knowledge owner, often a team lead who already knows where things live. That person watches the questions the assistant could not answer, sorts them into gaps in the material and questions that need a human decision, and passes them to whoever writes the policy or template. Over time the gaps become a rough map of what the organisation has never written down, which is often as valuable as the assistant itself.

Access follows roles as well. Reception can draw on different material from payroll, and when someone changes jobs, their access should change with them. Handled this way, people learn to check the source before acting on a reply.

good questions, straight answers

Frequently asked questions

How do I get my team to use Onyx?
Start with one question the team already asks often, such as where a policy lives or how a standard process runs. Choose one person to check answers and collect feedback, so corrections happen quickly. Keep the first group small, share a few examples of good questions, and widen access once the answers prove reliable. MILabs can help plan that rollout with the owner.
Can I self-host Onyx?
Yes. Onyx is a self-hosted platform, so it runs on servers the business controls rather than only in a vendor's cloud. Self-hosting gives the owner more say over where documents and conversations are stored, but someone must install the software, apply updates, manage backups and watch access. For a business without an internal IT role, that work is often better handed to a provider. MILabs can plan the hosting with the owner.
Which builds work well with Onyx?
Builds that answer questions from a body of private material suit Onyx best. Examples include a staff knowledge assistant for policies and procedures, a document question and answer server for files that must stay in-house, and a compliance checklist assistant that points people to the right clause. A client FAQ assistant works well once approved answers are clear and kept current. Builds that need many live integrations are scoped separately.
What is Onyx?
Onyx is software a business installs on its own servers to build and run AI assistants. Those assistants can work with the company's own information, and the company decides where that information is kept. Unlike a general chat tool used only through a website, it suits setups where the company controls storage and access. It fits teams with some technical capacity and a clear need for private, internal answers.
How does MILabs set up Onyx?
MILabs begins with the owner or team lead, agreeing the problem the assistant should solve and the information it may use. Hosting is chosen and existing systems are connected, with each source checked. Permissions are set so people see only what they are allowed to read. The owner and MILabs agree who looks after updates, backups and access reviews. MILabs is a Sydney agency, and work for clients outside Sydney is delivered remotely.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.