OpenDots self-hosted AI agent for small business
How a small business can evaluate OpenDots, a self-hosted agent, and how MILabs sets it up on infrastructure the business controls.
Updated 2026-02-06
What OpenDots is
OpenDots is a self-hosted agent project from CopilotKit, published openly on GitHub. An agent is software that takes a request, works through a sequence of steps, and returns a result, often by calling other systems along the way. Self-hosting means the software runs on servers that the business or its IT provider controls, rather than only on a vendor's cloud. For some businesses that difference matters, because the questions asked of an assistant, the documents it reads and the records it writes can stay inside infrastructure the business already governs. Teams usually look at a tool like this when they want an assistant that follows their own rules and keeps their records in-house. Which features suit a given workflow is a question for the scoping conversation, and that is where the specifics get settled. MILabs, a Sydney agency that helps small and mid-sized businesses use AI, treats OpenDots as one option among several. The choice depends on where the data lives, who maintains the software, and which models the business is willing to connect.
OpenDots in plain language
OpenDots belongs to a category of agent software where the coordinating code runs on infrastructure the business chooses. An agent of this kind receives a request, decides which tool or document it needs, and assembles a reply from the results. The language model that does the wording is usually a separate service, so a deployment is several parts working together: the agent logic, the model connection, the data sources and the people who approve output.
For a non-specialist, the most useful lens is ownership. Someone has to install the software, keep it patched, decide how it is backed up, and confirm who can reach it. Logs record what the agent was asked and what it did, so they deserve the same care as the records the agent reads. Those responsibilities are the price of holding the data inside your own environment.
Open source publication answers one question and leaves others open. Reading the code shows how it works, while the license file sets what you may do with it. The current documentation describes what a given release supports, and a feature mentioned in an article or discussion thread may not exist in the version you deploy. The repository's own documents are the most reliable reference point.
What businesses use it for
- Drafting first answers to staff questions from the business's own procedure documents
- Triaging enquiries that arrive through a website form or shared inbox
- Checking submitted paperwork against a written compliance checklist
- Keeping client-facing answers consistent with approved wording
- Running internal assistants where customer or staff records stay on company servers
Who it suits
- Businesses whose client or staff records must stay on infrastructure they control
- Teams with an IT provider or technical staff who can run and update the software
- Organisations that want to try an agent on their own documents first
How MILabs sets it up
MILabs begins with the owner or team lead, agreeing what the agent should handle and what should stay with people. Next, we confirm the hosting arrangement with whoever runs the company's infrastructure, including where the software runs and who holds its credentials. We then connect the systems the business already uses, such as email, shared drives, customer records or accounting software, limiting each link to the data the task needs. Permissions are set by role, so staff see only what their work requires, and any step that writes to a record can sit behind an approval the business chooses. Finally, we agree who handles updates, monitoring and changes once the agent is live, and write that down so the arrangement never depends on one person.
Builds it fits
Industries it fits
OpenDots in practice
A business starts with documents its staff rely on: handbooks, product sheets, approved wording and internal policies. An assistant built on the agent can answer staff questions by pointing back to those sources. When the material does not support an answer, the assistant says so and passes the question to the responsible person.
Messages from the contact page and the general mailbox arrive, and the agent proposes a category, a draft reply and a note for the team member who owns that topic. Staff edit the draft and send it themselves, so every reply is reviewed before it leaves the business.
Compliance checks follow the same pattern. The business writes a checklist of what a submitted form must contain, and the agent compares each submission against it, flagging gaps for a person to resolve. Because the checklist is the authority, keeping it current is the main maintenance task when rules change.
Running this well depends on habits more than software. A named person samples answers regularly, source documents are refreshed when policies change, and the list of systems the agent may read or write stays short and written down. Access is reviewed whenever someone changes role.
Frequently asked questions
- Can MILabs build on top of OpenDots?
- Yes, where the project's license permits the intended use. MILabs first confirms that the features a business needs exist in the released version, then designs the assistant around them. Builds usually combine the agent with the business's own documents, systems and approval steps. If a needed feature is missing, MILabs says so during scoping and suggests another option or a custom development approach.
- What does an OpenDots setup need from me?
- It needs a named owner who can make decisions about scope, access and data, and someone who can confirm hosting with your IT provider or internal team. You also list the systems the assistant should read from or write to, and the documents it may use. Agree in advance who approves changes and who watches the agent after launch. MILabs handles the configuration and documentation, and the business keeps responsibility for its data.
- What does OpenDots not do?
- OpenDots leaves the hosting to you. It is self-hosted, so your business runs the servers, applies the updates and decides who gets access, which gives you full control over where everything lives. An agent built on it is as capable as the models and integrations you connect, so picking strong ones lifts everything it does. MILabs names any gap found during scoping, so you start with a clear picture of the fit.
- Is OpenDots suitable for a small business?
- Yes, particularly for a small business that handles sensitive records and has access to someone who can run server software. For a business without technical support, a hosted product may be simpler to operate, and MILabs will say so and recommend it. The fit depends on the volume of work, the data involved and who looks after the system once it runs.
- Is OpenDots safe to use with customer data?
- Self-hosting gives a business control over where customer data is stored and which services receive it, and that is a sound starting point. Protection then depends on the server configuration, access controls, the model providers connected to the agent and how logs are handled. MILabs reviews those choices with the business before any customer data is used. No software can be declared safe in general, so this page makes no such guarantee.
