I made a bot that deploys to Kinesis for you

I’ve been using coding agents to build apps, then clicking through the Kinesis portal myself to get them online. The repo is done. The Dockerfile is done. And I am still the one in the wizard.

A coding agent can design the app. It cannot, by itself, be the person signed into kinesis portal. That gap is what Kinesis Portal Bot is for.

A coding agent can design the app. It cannot, by itself, be the person signed into kinesis portal. That gap is what Kinesis Portal Bot is for.

You add the bot, you sign in as yourself, and it clicks the portal on your account. Not a shared bot login. If the session is logged out, it stops and asks you to sign in. It will not click spend, wallets, or listing agreements without a yes. It does not hold wallets, provision tokens, or card numbers.

Kinesis is a grid for compute. You push a container or a GitHub repo. It places the work on a machine you already own, or on hardware you rent, and you pay for what actually runs. The portal is where that happens. The bot is just you, clicking it, without you having to learn the wizard.

Here is what I actually ran.

A coding agent built a static Three.js “scroll to walk” site: Vite, nginx in a multi-stage Dockerfile, sitting in a private GitHub repo. I had a Raspberry Pi sitting idle. Portal Bot connected my GitHub, brought that Pi onto Kinesis, and launched the site onto it — my own ARM box, on a grid I already had. There was no cost, because it was my device.

The first image was amd64. The Pi is arm64. Runtime said exec format error. We rebuilt linux/arm64 nginx, told the bot to Restart, and the logs went to clean 200s. It stayed Running, 1/1 online, nginx on HTTPS at *.apps.kinesiscloud.com.

That is the loop I wanted. A coding agent writes the image. Portal Bot ships it under your login. The builder never needs portal credentials. The portal bot never needs to invent the app.

Add the bot. Sign in as you. Then say what you want.

You don’t learn the wizard. You don’t need to know which tab is Logs. If the portal shows a price, the bot reads it and waits before Launch. If it needs a yes, it asks. Then it clicks.

Ask it to run a repo on a machine you already have. Ask it to rent something if you don’t have a box — it quotes first, then waits. Ask it to pull logs or restart when something is broken. Ask how an app is doing. Ask it to list idle GPU.

Idle hardware is the path I already ran: a Pi, a GitHub repo, no cost. Renting is the other path, and the bot will quote whatever Kinesis shows on the screen before it spends anything. If you want idle compute listed so someone else can rent it, ask it, then read the agreement yourself. It will not tick that for sport.

Anything else, ask the bot. That is the whole trick. It can see the live screen.

Portal: portal.kinesis.network

Docs: docs.kinesis.network

Bot: x.ai/bot/-GgufM3GkZclfn9PuI17_