Skip to content

What is Victor?

Victor is a modular business application: the features you use are installable apps, and AI agents work alongside you directly on your data. Instead of buying one rigid product, you assemble the apps your team needs — contacts, a helpdesk, whatever fits your work — and Victor gives every one of them the same screens, navigation, and built-in assistant automatically.

Two ideas make Victor different from a normal SaaS tool:

  • Everything is an app. A capability is added by installing an app (also called a module). Your Contacts app, your helpdesk, and even the admin screens are all apps built from the same pieces. You install the ones you want and can build your own.
  • Agents live inside your data. Victor's assistant isn't a bolt-on chatbot. It can read and act on the same records you see on screen, search your knowledge bases, and remember what matters across conversations.

This page gives you the mental model. Once it clicks, every screen in Victor reads the same way.

Your instance is your workspace

When you start with Victor you get an instance — your own private, isolated workspace. Your instance has its own data, its own installed apps, its own agents, and its own users. Nothing in it is shared with anyone else's instance.

You manage which instances exist from your Victor Cloud project, and the apps your instance runs come from that project's git repository: the apps you add to the repo are the ones your instance loads. Built-in apps like Contacts are there from the start; anything you build or install layers on top.

One instance, many apps

Think of the instance as the building and apps as the rooms you furnish it with. You can install more apps, upgrade them, or remove them at any time — see Administering your instance.

Apps are made of records

Almost everything you look at in Victor is a record — a single contact, a single support ticket, a single agent configuration. An app defines the kinds of records it holds (its models) and the screens for working with them:

  • A list or board shows a collection of records so you can scan, sort, filter, and search them.
  • A form shows one record so you can read and edit its fields.

You never learn a bespoke interface per app, because every app is rendered from the same building blocks. A helpdesk app might define a ticket record with a subject, a priority, and a linked customer; the built-in Contacts app defines a contact record with a name, an email, and tags. Both get a list, a form, search, and navigation for free. How those screens work in detail is covered in Navigating the app.

Moving around: the app shell

Every instance opens into the same layout. A left navigation rail lists your apps; the main area shows whichever app you've opened.

Region What it is
Left navigation Your installed apps, top to bottom. Click one to open it.
Main area The open app's records — a list or board, and the form when you click into a record.
Modules and Settings Two items pinned at the bottom of the navigation for managing the instance.
Ask Victor A button at the foot of the navigation that opens a conversation with Victor's assistant.
Theme toggle Switches between light and dark mode.

Moving around is just clicking:

  1. Pick an app from the left navigation to open its records.
  2. Some apps open straight to a collection; others group several screens as tabs on one page (the Settings area works this way).
  3. Click a record to open its form, then edit and save it.

The two pinned items at the bottom are how you run the instance itself: Modules is the Module Manager, where you install, upgrade, and remove apps, and Settings is a tabbed page for instance-wide configuration, permissions, and your agents. Both are covered in Administering your instance.

Agents work inside your data

Ask Victor opens a conversation with Victor's built-in assistant. Because the assistant runs inside your instance, it can do more than answer general questions — it can work with your actual records: look things up, draft replies, and carry out actions you'd otherwise click through by hand. Before it does anything consequential — changing a record or reaching outside your instance, like sending an email — it pauses and asks you to approve; read-only lookups never interrupt. See Agents, knowledge & memory for how approvals work.

An agent is a configured assistant. Each one has a model, instructions, and a set of abilities:

  • Tools let an agent read and change records — for example, look up a contact or send an email. The built-in assistant automatically gains the read-only tools of every app you install, so newly installed apps light up in conversation with no setup.
  • Knowledge bases give an agent reference material — documents and text it can search to answer accurately.
  • Memory lets an agent remember durable facts and preferences across conversations, so it doesn't start from zero each time. Remembered facts are confirmed by a person before Victor relies on them.

Agents are themselves ordinary records you can view and edit under Settings → Agents, alongside their Skills and Tools. You can tune the built-in assistant or create your own agents for specific jobs. See Agents, knowledge & memory for the full tour.

How it fits together

The three ideas compose into one loop:

  • Apps define the kinds of records your team works with and the screens for them.
  • Records are the actual data — the contacts, tickets, and everything else you create day to day.
  • Agents work over those same records, with tools to act, knowledge to consult, and memory to stay consistent.

Add a helpdesk app and you instantly have a place to track ticket records and an assistant that can triage them, look up the linked customer in Contacts, and pull answers from your support knowledge base — all without wiring anything together. Install another app and its data and tools join the same environment.

Who Victor is for

  • Teams who want a business application shaped around how they actually work, rather than bending their process to fit fixed software — and who want an AI assistant that operates on their real data, not a generic copy of it.
  • Builders — the person on the team who assembles the instance: installing apps, configuring agents, and extending or creating apps to cover the gaps. No frontend code is involved; apps are declared, and Victor renders them.

If you use Victor day to day, the User Guide is for you. If you assemble or build the apps, the Developer Guide picks up where this leaves off.

Where to go next

User Guide — using an instance:

Developer Guide — building your own apps:

  • How modules work — build a working app from a model and a few views, with a 5-minute helpdesk quickstart.