Capability

Every script in one place, written with you

A library for every script your team runs on its servers: written with the agent or by you, organised in groups, every version kept, run with one click.

Create account See the full flow

Bash PowerShell Batch Python Node.js Linux and Windows servers Your own machine

In your words

Ask it like this

No syntax to learn. These are real requests, phrased the way people actually phrase them.

›write a backup script for the database on db-1 ›show me the deploy scripts for staging ›change the log cleanup to keep 14 days ›what changed in this script since last week ›run the cache clear on all web servers ›add the script in /opt/tools to my library

Capability

What it does here

Everything below is what the agent does today, not a roadmap.

Ask for a script and the agent writes it, then shows it to you to approve before it is saved
Organise scripts in groups, each tied to the server it runs on
Edit them in the app, with line numbers, colours, find and replace, and Ctrl+S
Every save keeps the old version in History
Risky commands are pointed out while you write, and a file changed on the server is never overwritten silently
Run with one click, or ask the agent, and watch the output live

What it looks like

One question, one answer, one fix

The checks on the left of each reply are the reads it did before committing to an answer. That is the difference between a diagnosis and a guess.

Every exchange ends in a verified outcome. It goes back and confirms the result rather than assuming the fix worked.

brynko devOps Agent

write a script that backs up the shop database every night to /backups

checked db-1 found MySQL 8 drafted the script

Here is a Bash script for db-1: it dumps the shop database, compresses it, keeps 14 days and logs the result. Approve it on the card and it is saved under Backups.

keep 30 days instead

edited the script showed the diff

Changed to 30 days; the diff is on the card. Once you save, the old version stays in History.

Saved · Backups

Common cases

The ones that cost you an afternoon

Each of these is a specific failure with a specific set of checks behind it, not a general promise to help.

Scripts are scattered across servers

Each server has its own folder of scripts, and nobody is sure which one is current.

What it does. Every script sits in one library, in groups, each tied to its server, with the path it runs from.

Writing a script takes an afternoon

The task is clear, but the flags, the error handling and the Windows version are not.

What it does. Describe it and the agent writes it for the right server and language, shown to you before it is saved.

Someone changed it and it broke

The script worked last week and nobody knows what changed.

What it does. Every save keeps the old version in History, so you can see what changed and when.

Editing on the server is risky

An edit in a terminal editor, a typo, and the deploy fails at the worst moment.

What it does. You edit in the app, risky commands are pointed out as you type, and a file changed on the server since you opened it is never overwritten without asking.

Only one person knows how to run it

The right script, the right folder, the right order: it lives in one head.

What it does. Anyone runs it from the library with one click, or asks the agent, and sees the output as it runs.

Existing scripts are already in use

There are years of scripts that work, and rewriting them is not on anyone's list.

What it does. Add an existing file to the library as it is; it keeps working from where it lives.

Start to finish

What happens between the question and the fix

You describe the job
Or add a script you already have.
The agent writes it
For the right server, language and path.
You review and save it
Shown in full before it is saved; edits show as a diff.
It lives in your library
In a group, with every version in History.
You run it
One click, or ask, with the output live.

The part that matters

Reading is free. Changing asks first.

Reads run instantly and need no permission, because reading cannot break anything. Anything that changes a system, whether that is a restart, an edit, an install or a delete, stops and tells you what it is about to change, on which server, and why. You see it written out, as the command it will run or a red and green diff of the file, so you are approving the actual thing rather than a description of it. Changes are backed up first, so undoing one is a click.

Read the security model

Questions

Scripts, specifically

Can I write scripts myself too?

Yes. New script asks for the name, server, language and where to save it, and opens the editor with a starter for that language.

Does it overwrite a script someone changed on the server?

No. If the file changed after you opened it, you are asked before anything is written.

Can I use the scripts I already have?

Yes. Add an existing file to the library and it runs from where it is.

Does the agent save scripts without asking?

No. A script the agent writes or edits is shown to you first, and saved only when you approve it.

Which languages?

Bash, PowerShell, Batch, Python and Node.js, on Linux and Windows servers or your own machine.

Can a script run on a schedule?

Not from the app yet. You can run any script with one click or by asking; for a schedule, keep cron or Task Scheduler and let the agent write the entry for you.

Also covered

The rest of the stack

Ask your database what is wrong

Read-only checks and queries over your existing SSH connection, with credentials encrypted at rest.

Wildcard HTTPS, sorted in one step

Issue trusted, auto-renewing certificates, wildcards included, and get the paths handed straight back.

Your AWS account, in plain English

Read EC2, S3, Elastic IPs and EBS, spot what is quietly costing you money, and make changes only after you approve them.

Ask Jenkins what went wrong

Read jobs, builds, the queue and console logs, find out why a build failed, and trigger or stop builds with your approval.

It runs on your machine too

Build, run and fix projects on your own computer, including installing the runtime the project needs.

A real file editor for your Linux servers, no nano required

Browse your Linux servers as a file tree and edit files in a real editor with syntax highlighting, find and replace and search across the whole box. Over the SSH access you already have, with nothing installed on the server.

Try it on something that already annoys you

Point it at one server. You will know within an hour whether it earns its place.

Create account See pricing