Maıestro Tech Book a walkthrough

Security Controls and boundaries

Built for systems you cannot afford to break.

Ensemble works on the software a business runs on. So the rules that keep it safe are enforced by the platform, not left to a prompt and a model's good intentions.

01 Controls

Eight controls that hold on every engine.

  1. Production is read-only

    Database access goes through a separate reader service on a local socket, under its own account. Each call is one SELECT, validated before it reaches the database, capped at ten seconds and a bounded number of rows.

  2. No permanent installs by agents

    The Tester installs packages only on an isolated copy and removes them when the run ends. Going live on staging is a person's click. Production changes leave as a script for review.

  3. Sign in with your directory

    People sign in with their existing LDAP or Active Directory account. Ensemble does not store passwords.

  4. Least privilege by default

    Tool access is set per role and per user. Agents run as an unprivileged system user with no sudo. File tools stop at the agent's workspace and the folders you allow, and read bans apply on every engine.

  5. Personal data masked before indexing

    E-mail addresses, user codes and national ID numbers are masked before anything enters the search index. System accounts are recognised and left alone.

  6. Secrets and clutter stay out of sight

    Connection details are masked wherever an agent could read them. Test, inactive and backup objects are hidden from agents entirely, so they are never copied by mistake.

  7. Every action recorded

    Every run, message, tool call, result and token count is stored with its conversation. You can replay what an agent saw and what it did.

  8. Your model, your boundary

    Use a hosted model, or keep every byte inside your network with a local model.

02 Guarantees

Things that do not happen.

These are properties of the platform. They hold on every engine and every model, whatever a prompt says.

None of these happen.

  • An agent writes to your production database.
  • A test install stays behind after the run.
  • One person's preference becomes another person's instruction.
  • Memory overrides a sealed spec.
  • A new engine version goes live without being tried first.
  • A password is stored.

03 Shared responsibility

Where our boundary ends and yours begins.

Ensemble

Takes care of
Read-only access, tool permissions, isolated testing and cleanup, masking, the record of every action.

Your model provider

Takes care of
What happens to the prompts an engine sends. Their terms apply. Choose a local model where that is not acceptable.

Your team

Takes care of
Who gets which role, which folders agents may read, and the final review of every production script.

Bring your security team.

We'll go through the architecture, the accounts and the logs with them, on your terms.

Book a review See the architecture