Everything the platform does

Push to deploy

Push to your branch and Tensel builds that exact commit and rolls it out.

Every environment on the branch deploys

One push deploys every environment bound to that branch, not just the first one.

Repository import

One command or one click creates the project, the application, the environment and the first deployment.

Deploy a folder, no git required

Drop a folder in the browser or point the CLI at a directory; it is packed, uploaded and deployed.

Framework detection

The builder, runtime kind, build command and output directory are read from the repository.

Dockerfile builds

A Dockerfile wins when present; your image is built as written.

Builds without a Dockerfile

Node frameworks are detected directly; Go, Python, Rust, PHP, Java and Ruby build from their marker files.

Toolchain read from the repo

.nvmrc, engines and packageManager decide the Node version and package manager, not a platform default.

Overridable build settings

Override the builder, root directory, commands, output directory or Node version; what the engine resolved stays visible next to your override.

Monorepo root picker

Browse the repository tree and pick the directory an environment builds from.

Isolated builds

Every build runs in a disposable virtual machine, destroyed after use, with no access to platform networks.

Zero-downtime rollout

A new version replaces the old one only once it answers healthy; a failed deploy never takes the site down.

Rollback to any revision

Every revision is an immutable image; roll back to the exact state of any earlier deployment in one command.

Cancel in-flight deployments

A queued or building deployment can be cancelled before it lands.

Builds survive platform releases

When Tensel itself deploys, your in-flight build resumes instead of failing.

GitHub Checks

The deployment result reports back on the commit as a check, next to your CI.

Auto-deploy pause

Pause an environment and pushes stop deploying it; every ignored push says why it was ignored.

Serverless containers

Each environment runs in its own container in Paris, never a shared process between customers.

Scale to zero

An idle application sleeps and costs nothing to run; the first request wakes it in one to three seconds.

Always-on

Keep one instance resident so no request ever waits for a cold start.

Automatic sizing

Every environment starts small and is stepped up under sustained memory pressure; pin a size or leave it automatic.

Scale-out under load

Replicas are added when concurrent requests climb, within the size's envelope.

Static sites without a container

Static frameworks are detected and served from a shared always-on edge. No cold start, and no bill.

Static sites answer agents in Markdown

Ship a Markdown copy of a page beside it and the edge serves that to clients asking for Markdown, and the HTML to everyone else. Nothing to switch on.

European CDN for static sites

Static delivery from European points of presence, EU-routed by default; global routing is a per-environment opt-in with a disclosure.

Isolated environments

Each environment has its own branch, configuration, secrets, hostname and logs; production cannot be deleted by accident.

A tensel.cloud hostname from day one

Every environment gets a stable subdomain on its first successful deploy, and keeps it across renames.

Custom domains

Point your DNS at Tensel and the domain serves your environment.

Automatic TLS, free

Certificates are provisioned and renewed for you; there is no certificate line on any invoice.

Apex domains

Bare domains work, not only www: the apex is detected and served via ALIAS.

A stable edge CNAME

Your DNS points at a Tensel-owned name, so infrastructure moves behind it never touch your zone.

DNS re-check on demand

Check now instead of waiting out the backoff when you have just fixed a record.

Build logs, step by step

Fetching source, building, publishing, going live. The same grouped log in the dashboard and the CLI.

Live log streaming

Logs stream as they happen; --follow resumes where it left off after a dropped connection and stops on its own when the deployment ends.

Application logs per environment

A running container's output belongs to its environment, not to whichever deployment happens to be live.

Runtime metrics

Requests, CPU, memory and instance count, read on demand from the host. Tensel ingests nothing and retains nothing.

Sleep shown as sleep

A scaled-to-zero application renders as asleep, never as an outage.

Seven days of runtime logs, included

Runtime logs are part of the platform, not a metered add-on; build logs are kept 30 days, and the live deployment's log for as long as it serves traffic.

Organisations, projects, applications, environments

One hierarchy for everything; every resource has one obvious place.

Members and roles

Owner, developer and viewer roles, checked as permissions on every action.

Email invitations

Invite by address, set the role, revoke or resend. The invitee needs nothing installed.

Passwordless sign-in

Magic link or passkey; Google and GitHub are optional. Identity runs on our own infrastructure, not an identity SaaS.

CLI sign-in without a password

tensel login opens your browser and you approve the device there; nothing secret is typed in a terminal.

API keys

Named, revocable keys with last-use tracking, shown once at creation.

One year of audit log

Sign-ins, role changes, secret writes and deployments, immutable, with names resolved even after the thing was deleted.

Organisation export

Everything about your organisation as JSON: secret names included, secret values never.

Deletion that cleans up

Deleting an application tears down its runtime and DNS in the same transaction, after a recovery window.

Environment variables with a scope

Each variable is visible at build time, at runtime, or both. You choose, per variable.

Write-only secrets

Set once, encrypted before they reach the database, injected at deploy. There is no way to read a value back.

dotenv import

Import an existing .env in one command instead of retyping it.

Secrets never in logs

Secret values are masked in the dashboard and absent from every log line the platform writes.

Subscription matched in usage

You pay whichever is higher: the plan, or what you used. Never both.

Four meters, nothing else

Runtime, builds, storage and transfer are metered; domains, TLS, logs and metrics consume nothing.

Static sites are never billed

Static builds, storage and delivery consume none of your allowance, on every plan.

The free plan cannot bill you

A free organisation's usage is measured, then written off. There is no path from the Free plan to an invoice.

A hard spend limit you set

Default 2× your subscription, adjustable; warnings at 50, 75, 90 and 100 percent.

24 hours of grace at the limit

At 100 percent, new paid actions stop and running apps get a visible 24-hour grace. Usage during the grace is absorbed, not billed.

Usage by day and by project

See which project spent what, day by day, against your allowance and your limit.

History at the prices of its time

Closed periods are shown exactly as they were rated; a price change never alters a closed invoice.

Factur-X invoices

Invoices are PDFs carrying the EU e-invoicing XML, ready for your accounting software.

Anniversary billing

Your cycle starts the day you subscribed, not on calendar months.

European payments, EU VAT handled

Payments run through Mollie (Amsterdam); VAT numbers are checked against VIES and the invoice is right for your country.

Cancel monthly

No annual commitment; cancelling takes effect at the end of the period you paid for.

A French company under EU law

Tensel is operated by a company incorporated in France, subject to European Union jurisdiction.

Workloads and platform data in Paris

Applications, builds, images, database, secrets, backups and logs are hosted in Scaleway's Paris region.

Every subprocessor documented

The full register is public, and every subprocessor is European; the one optional US integration (GitHub) is disclosed as such.

GitHub is optional

Deploy from a folder and no code ever touches a US service; enabling auto-deploy is your call, and disclosed.

EU-routed delivery by default

The static CDN serves from European points of presence; routing beyond Europe is an explicit opt-in.

No trackers

This site sets no analytics cookies and loads nothing from a third party.

Restore proven by drill

Backups are restored for real on a schedule, and the last drill's time to verified data is published.

Leave in standard formats

Configuration and data export as JSON, images are OCI images, cancellation is monthly. No proprietary format anywhere.

Complete CLI

Deploys, environments, domains, members, billing, audit: everything the dashboard does is a command.

--json everywhere

Every read command emits documented JSON; the prose output is for humans and may change, the JSON shape is the contract.

Human-readable references

Commands accept org/project/application/environment references the way you would say them.

Eleven agent skills in the box

The npm package ships skills for deploying, domains, logs, billing and more; one command installs them for your agent.

Skills hold no credentials

A skill drives the CLI and never calls the API itself; tensel login stays the only path a credential takes.

Skills that know the limits

Each skill states what the platform cannot do, so an agent asks you instead of inventing a workaround.

CI-ready

A revocable API key via TENSEL_TOKEN, and --api-url to point anywhere a Tensel runs. Your session token never leaves your machine.

Destructive commands ask first

Deletions prompt for confirmation; --yes exists for scripts that mean it.

Dashboard in French and English

The web dashboard ships both languages, chosen on the device.