The AI-native app platform
The AI-native app platform your IT team will approve, and love. Describe the app you have always wanted. Your AI builds it, and Gliss puts it live, signed in and backed up, without a single ticket.
Works with the AI you already use: Claude, Cursor and Codex, on Mac, Windows and Linux.
gliss.
/ɡlɪs/ · short for glissando /ɡlɪˈsændoʊ/
In music, a glissando is a glide from one note to another: a finger sweeping up the piano keys, or a hand running across a harp's strings. Every note in between still sounds, in one smooth motion.
That's what Gliss does for apps. Every step between your idea and a live app still happens: building, testing, sign-in, security checks, your IT team's approval. You glide through them instead of stopping at each one.
The problem
Everyone can build an app in an afternoon now. Then the app needs a home, a login, a key, an owner and someone to keep it running. IT is left with two bad choices: say no, or inherit the mess.
Gliss is the third choice: say yes, and stay in control.
Every AI in Gliss is yours
Claude, Cursor or Codex writes the screens and the logic, and asks Gliss for everything else in a few lines.
Each upgrade, publish and exception arrives as a short decision packet. IT's AI reviews it and recommends; a person approves.
They watch, find the cause and propose the fix, on your own AI account, with every step on the record.
No vendor model reads your code, your data or your logs. Gliss makes the AI your company already approved safe to build with.
Your AI turns your needs into code. Gliss makes it real.
Most of an app is plumbing: logins, databases, keys, hosting, backups. With Gliss, your AI asks for those in a few lines and gets them, approved and running. It spends its effort on the screens, the experience and the rules that make the app yours. The app is smaller, faster to build and much less likely to break.
apiVersion: gliss.dev/v1 app: expense-tracker owner: maya@acme.com components: web: { build: ., port: 8080 } capabilities: database: { type: postgres } auth: { type: sso, audience: org } site: { type: hostname, name: expenses } secrets: { STRIPE_API_KEY: credential } healer: { level: propose }
No corporate friction. No DevOps.
Your private copy, updated as your AI works. Every change is live in seconds. Nobody else sees it.
Keep buildingShare a link with the colleagues who will use it. They sign in with their work account and tell you what to change.
Share to BetaPress Publish. Gliss checks that it's healthy, tested and complete, then puts exactly what you tested live.
PublishNobody has to set up a server, a database or a domain for you. You ask, Gliss provides, within what IT allows.
Need an API key from finance? Send them a link. The key goes straight into your company's vault, and your AI never sees it.
Review and accept changes in Gliss. Your company sign-in and your AI tool are all you need. No cloud console, no Kubernetes.
Gliss always says whose problem it is. When the platform needs fixing, that lands on IT and the healers, never on you.
Apps that stay alive
Gliss local healers watch every app and the platform underneath it, inside your own account and on your own AI account. When something breaks, they find the cause, write the fix and prove it before anyone sees it. They hold no keys and change nothing on their own: they propose, and you or your policy decide.
gliss heal review 4812For your IT team
Your colleagues want to build apps with AI. Gliss lets you say yes without becoming DevOps or platform engineers. Everything runs in your own cloud account, under your sign-in and your rules. You make the decisions, your AI reads them first, and the platform does the work.
One CloudFormation launch installs the platform. Apps, data and secrets stay in your account. The Gliss cloud coordinates releases and never needs a way in.
People sign in through your company's identity provider, such as Microsoft Entra ID. Who can see an app, and what they can do in it, comes from your groups.
Databases, sizes, which outside services apps may call, and what needs your approval, such as public apps. Anything not on the menu is refused before it's built.
Upgrades, publishes and exceptions come as decision packets your AI can review over MCP or the CLI. A person approves with one click.
Every change that reaches your cluster is signed and checked. A leaked token or a confused AI can't deploy around your rules.
Each app has an owner, a health status and an audit trail of who changed what, and when.
Every fact the Gliss cloud holds about you is on one page in your console, with a log of every person on our side who looked.
Tested platform upgrades, an upgrade-risk check of every app, and Gliss local healers on your AI account that act on what they find. Let the healers work, or have your own team act on the findings.
| Where it runs | What's there | Who controls it |
|---|---|---|
| Your AWS account | The apps, their databases, files, secrets, logs, backups and the healers' records | You. We can't read your secrets or your data. |
| Your GitHub | The code of every app, in your organisation's repositories | You |
| Your AI accounts | The models your builders, your IT team and the Gliss local healers use | You |
| Gliss cloud | App registry, approvals, release signing, a monitoring overview | Us, with access to your cluster only through a connection the platform opens. You see everything we see. |
| Your colleagues' laptops | Their AI tool and a small Gliss client | Them, signed in with their work account |
Why Gliss
Self-service apps usually mean building a platform team, or living with the shadow IT that comes from saying no. Gliss is the platform team, delivered as a product.
Early access
We're opening Gliss to a small group of teams first. Leave your details, tell us what you'd build first, and we'll be in touch when there's a place for you.