Fransys

Kubernetes without writing YAML

You place blocks on a canvas: applications, databases, networking. The platform writes the Kubernetes manifests, applies them and keeps them true. The YAML still exists, you just never type it.

No credit card, no commitment.

Stack diagramKubernetes without YAML
01

The canvas

02
  1. Applications
  2. Databases
  3. Networking
  4. Jobs
03

Kubernetes, built and run by Fransys

04

The European cloud you chose Scaleway · OVHcloud · Hetzner · Outscale

What Kubernetes YAML costs

Kubernetes became the orchestration standard, and its entry ticket never changed: hundreds of configuration lines where one bad indentation costs an evening. That toll filters teams by patience rather than by need. The canvas removes it without taking anything away from the engine.

  • 0lines of YAML to write
  • 100%of generated manifests exportable
  • 4block categories on the canvas

Four block categories

Everything that deploys is described with these four families.

  1. Applications

    Your code, from a Git repository or a Docker image. Resources, domains and variables are set inside the block.

  2. Databases

    PostgreSQL, MySQL, Redis as managed blocks, with backups configured in the same place.

  3. Networking

    Exposure, domains and TLS. Certificates are issued and renewed on their own.

  4. Jobs

    Crons and one-off tasks, with their own resource limits.

What the platform writes for you

From a placed block to an updated cluster.

  1. canvas

    You place or modify a block.

  2. generate

    The matching manifests are generated: deployments, services, ingress, autoscaling.

  3. validate

    The whole set is checked for consistency before anything is applied.

  4. apply

    The cluster converges to the described state. Version history is kept.

With your agent, or by hand

With your agentexample

Add a PostgreSQL database and a nightly cleanup cron.

  1. The agent prepares the two blocks; the platform derives the manifests from them.
  2. Consistency is checked, then a person approves.
  3. The cluster converges to the described state; the history is kept.

The airlock, in detail

By hand

  1. Place a Databases block, then a Jobs block.
  2. Set resources and backups in each block.
  3. The manifests are generated, checked and applied for you.

A tour of the canvas

Write the manifests, or generate them

YAML + KUBECTLManifests by handBLOCKS + GENERATIONFransys canvas
Access to every exotic option of the Kubernetes API ✓ ✕
Whole-set consistency checked before applying ✕ ✓
Readable by the whole team, not just the expert ✕ ✓
Standard, exportable manifests ✓ ✓
Indentation mistake possible on a Friday night ✓ ✕

What people ask about the canvas

Can I see the generated YAML?

Yes, at any time. The manifests are standard Kubernetes resources, readable and exportable. The canvas is an interface on top of the standard, not a proprietary format.

What if I need an option the canvas does not offer?

That is the acknowledged limit of the approach: the canvas covers the needs of the vast majority of applications; very unusual configurations fall outside it. If your need falls outside, talk to us about it: the honest answer may be that a hand-managed cluster suits you better.

Does the canvas replace GitOps?

It keeps the principle, a described and versioned state that the cluster converges to, without asking the team to operate the tools. The canvas change history is kept.

What happens if I leave Fransys?

You export the generated manifests and apply them wherever you like. This is the reversibility test we invite you to run as soon as you start the trial.

To go further: managed Kubernetes hosting in Europe.

Your infra on the canvas: where to start

See the console in demo, in your name. To cost your app, the infra plan does it line by line, machines included.

No credit card, no commitment.

Read on the blog

Product newsMarch 9, 20262 min

Release 1.1.0: Helm block, environment variable expansion and Cilium ingress

Release 1.1.0: deploy Helm charts inside Fransys, compose your environment variables and get a better-performing Cilium ingress.

Product newsFebruary 9, 20262 min

What's new on Fransys: PostgreSQL backups, autoscaling, GPUs and more

Disabling blocks, PostgreSQL backups with point-in-time recovery, Nvidia GPU support, cluster autoscaling and other new Fransys features.

AI and infraSeptember 29, 20265 min

Hetzner managed Kubernetes: what the provider does not do for you

Hetzner offers no managed Kubernetes. What you must assemble yourself for production, what it costs in engineering time, and when to delegate.