Fransys

Security · the airlock

What the agent is not allowed to do

The security we can show you is the airlock. Nothing goes from the agent to your production without passing through it.

No credit card, no commitment.

The agent's rights, in writing

  1. ReadAllowed

    Read, without waiting: logs, metrics, deployment history, costs.

  2. Prepare a planAllowed

    Prepare a costed plan, block by block.

  3. WriteNever alone

    Write to your production: never alone. The plan waits for approval from a person on your team.

  4. ExecuteNo

    Execute: no. The Fransys engine executes, a program with no AI.

  • The airlock: the agent reads, it does not write alone.
  • Without human approval, nothing executes.
  • The engine is code: the same action gives the same result.
  • You choose the provider and the country.
  • For sensitive data, Outscale is SecNumCloud qualified.
  • Standard containers and Kubernetes: you leave with your images and your data.

Five Kubernetes protections you don't have to wire up

  • TLS everywherecertificates issued and renewed automatically on every exposed service.
  • Per-project isolationeach project lives in its own network perimeter.
  • Least privilege (RBAC)human and application access is scoped to its role, per project.
  • Maintained coresecurity patches for the Kubernetes core are applied.
  • Secrets out of the reposensitive variables are stored on the platform side, never in the code or the image.

Where your servers are

At the European provider you choose: Scaleway, OVHcloud, Hetzner or Outscale, in France, Germany, Finland or Poland. For sensitive data, Outscale is SecNumCloud qualified.

Choose your European cloud

France Germany Poland Finland
SecNumCloud For sensitive data, Outscale is qualified by ANSSI, with datacentres in France.

During an incident

A write by the agent always waits for a human. For an incident, the platform does not wait: it sees it, takes the first step, and the team takes over, day or night.

  1. Before

    Data and configuration are backed up according to the policy set on the canvas.

  2. The incident

    The platform sees it before you do, and takes the first step: a service restarts, a production release that breaks reverts to the previous version.

  3. The rollback

    Going back to a previous version takes a single action.

  4. Then

    The team is alerted and takes over, day or night. Then a written report.

What happens, step by step

If you leave

Your applications run in standard containers, on Kubernetes. You leave with your images and your data. There is no lock-in period.

Your questions

What is the agent allowed to do?

It freely reads logs, metrics, history and costs. To act, it prepares a costed plan, which someone on your team approves before the Fransys engine, a program with no AI, executes it.

Do you migrate our current cluster?

No. The platform does not take over a cluster already in place: it deploys from your repository, onto a new cluster. What our DevOps as a service covers.