Your records, held together.
A workspace holds your records, files, business rules, and history in its own folder. The information stays together even when you use different applications to work with it.
Stellar / The Stackworks platform
Stellar
Your data and rules.
Working together.
Stellar keeps your data, business rules, and history in one place. We call that place a workspace.
Your applications and AI tools connect to that workspace. They use the same records and follow the same rules. Stellar powers Wilson and the custom systems we build for our clients.
The architecture
One place for the records.
One set of rules.
Every application connects through the same API: the way software reads information and requests changes. Stellar checks who is asking and whether the change is allowed.
Stellar architectureHow the parts connect
PeopleApps & websites
AgentsInformation & permitted tools
Shared APIRead information · Request changes
Stellar workspaceRules & permissions checked here
RecordsData & links between records
Business rulesChecks on changes
AccessPolicies & permissions
HistoryPast changes & source information
Events & schedules → Agreed actions
Workers & integrationsModels · File processing · External servicesRead and write through the API
Your records and rules stay in the workspace. Apps, AI assistants, and workers connect through the API.
Every change is checked.
Whether a request comes from a person or an AI assistant, the API checks the same permissions and business rules.
Computers that carry out tasks.
A worker is a computer that runs tools, processes files, or executes code. It can be your own machine or one we host. It uses the API to read or update the workspace.
Your data & AI
Give AI the information it needs.
Keep control of your records.
Your workspace keeps the records. AI can read the information it needs and request actions through the API. Stellar checks those requests before allowing changes.
We define which information each AI task needs, which provider receives it, and what the AI is allowed to do. Those choices are part of the project’s design.
Your dataStellar workspace
Records · Rules · Permissions · History
API Checks permissions & changes
Information needed for the task ↓↑ Result or requested action
Computer running the AI
On your own equipment or with a hosting provider, as agreed for the project.
A hosted AI service may receive information for the task. We specify what is shared and why, including whether the AI should run on your own equipment.
Control the records.
Agree where your data lives, who can access it, and how it can be recovered.
Limit what is shared.
Give each AI task the information it needs. Decide what can be sent to an outside service.
Choose where AI runs.
Choose your own equipment or a hosted service based on privacy, speed, cost, and support needs.
Seven concepts
Seven building blocks.
One consistent system.
These are the technical building blocks behind a workspace. They describe what is recorded, how changes happen, and who can make them.
ConceptResponsibilityWhat the system enforces
01 Entity
A record with defined fields and links to other records.
Fields must contain the right kind of information. Links must point to records that exist.
02 Posting
A record of a quantity moving between accounts.
Both sides are recorded together. The movement must satisfy the balance rules.
03 Transition
A change from one status to another.
The current status, required information, and related changes must all be valid.
04 Observation
Information received from an outside source.
The source is kept with the information, and the same fact is not added twice.
05 Trigger
An action that runs after an event or at a scheduled time.
Automatic actions follow the same rules as other requests.
06 Policy
The permissions given to a person or AI assistant.
An application or AI assistant cannot grant itself more access.
07 Read
An answer calculated from the records.
Reports and other answers use the source records, so they do not need a separate set of figures.
How an AI assistant works
AI can choose an approach.
Stellar checks the action.
An AI agent is an assistant that can use software tools to do work. It reads your request, gathers the information available to it, and chooses a tool. Stellar checks whether the requested action is allowed.
The assistant cannot give itself more access or skip a required approval. The workspace records successful changes so your team can see what happened.
- 01
Understand the request
The assistant reads the information it has permission to use.
- 02
Ask to take an action
The assistant calls a tool. Stellar checks permissions and business rules.
- 03
Record the outcome
The workspace records a successful change. If the request is refused or needs approval, the assistant receives that result.
Ownership & delivery
Your data stays yours.
We run the software.
You own your workspace data. You can keep a readable copy of your records, files, and history. The records use SQLite, a standard database format that can be read without Stackworks.
We own and maintain the software that runs Stellar. We normally host it for you. Your team connects through applications, the API, and computers authorized to carry out tasks.
Your data belongs to you; the Stellar software is licensed separately.
Running AI on your own computer is different from hosting Stellar there. We agree where each part runs before the system is installed.
Built on StellarWilson is the app and AI assistant your team uses to work with Stellar. We also build custom applications that connect to the same workspace.
Meet the product family ↗Let’s talk
Tell us about
your project.
Tell us what you want to build or improve, how your team works today, and what needs to change.
If you have a project brief or solicitation, include the documents, deadline, and required results.
Book a call below, or , our site assistant.
hello@stackworks.sh