It joins the team
Install it and it introduces itself in a DM, asks what the team is working on, and remembers the answers. Mention it in any channel. It learns your people, your projects, and how you like things done.
Now in preview · free while it lasts
The teammate that gets it done.
Aidney is an AI teammate your company hires into Slack. Hand it work in a thread. It plans, does the job across the apps your team already uses, writes code on its own machine, and reports back with its work shown.
- 2 minto hire and introduce
- 24/7on shift, checks in
- 100%of steps logged
Works where your team already works
- Slack
- GitHub
- Linear
- Notion
- Jira
- Google Calendar
- Gmail
- Figma
- Sentry
live today · the rest are next, and every app it connects to adds a thing it can do for you
How it works
Hire it like a person. Hand it work like a person.
There is no dashboard to learn and no prompt to write. Aidney lives in the place your team already talks, and it behaves like a careful new hire who wants to be useful.
It does the work
Research, writing, follow-ups, and real engineering. Say what you need in a thread. It makes a plan, does the job, and comes back with the result and a plain account of how it got there.
It works across your apps
Each app you connect adds an ability. Slack is where it talks. GitHub is where it codes. Calendar, mail, and your task tracker are where it keeps the rest of the week moving.
Engineering
Real code, on its own machine.
Connect a repository and Aidney gets a dedicated coding box. It runs real coding sessions there, the way a careful lead would: write the brief, supervise the run, review the output, report back.
- Work lands on a branch with a summary in the thread
- It never merges and never deploys. That step stays human.
- Every session has a live terminal you can open
$ bun test tests/signup.test.ts ✓ creates an account 41ms ✗ shows the welcome state flaky → the test reads the toast before the route settles $ git commit -m "signup: await route before asserting toast" $ git push origin fix/flaky-signup ✓ branch pushed · summary posted to #web
Integrations
Every app you connect is a new thing it can do.
Aidney has exactly the access you give it, and nothing more. Connect an app and it gains that app's abilities, with every action recorded.
Where it lives. DMs, mentions, threads, and a standing check-in on your schedule.
Coding sessions on its own machine. Branches, summaries, a terminal you can watch.
Pick up issues, keep them updated, and close them with the branch attached.
The same for teams on Jira: tickets in, work out, status kept honest.
Read the docs your team lives by, and write the ones it produces.
Find time, hold it, and prepare what the meeting needs before it starts.
Drafts and follow-ups in your voice. Nothing sends without you.
Turn a frame into a ticket, or a ticket into a first implementation.
A new error becomes a diagnosis, then a branch, then a message in the thread.
A day with Aidney
This is the real flow, not a demo reel.
You install the Slack app. Aidney introduces itself in a DM and asks what the team is working on.
joinsYou hand it work in a thread: the signup test is flaky again, can you take it?
assignmentIt starts a coding session on its machine, writes the brief, and supervises the run.
workingIt reviews the output and reports back: what changed, what it tested, and a link to the branch.
deliveredYour team reviews the branch and merges it. Aidney never merges and never deploys.
Its standing check-in lands: what moved, what is next, and anything it needs from you.
check-in
Trust
Easy to trust because it is easy to check.
Every step Aidney takes is recorded as it happens: messages, sessions, tool calls with their inputs and outputs, and the exact context it saw. Not a summary written after the fact.
It never merges or deploys
Finished work lands on a branch. Shipping it is always a person's call.
It has only what you connect
Slack, and a repository if you give it one. It cannot log into anything else.
Nothing leaves your workspace
No outside messages, no email on your behalf. What it writes stays with your team.
Spend has a hard cap
Budgeted per workspace. When the budget is spent it stops, and says so.
Get started
Hire Aidney in the time it takes to make coffee.
Install it, hand it something real, and read the log. It is a preview: free, budgeted, and fully observable from the first minute.
Add to Slack
no card · no setup call
- 1Sign in and name your company
- 2Connect Slack. Aidney introduces itself.
- 3Hand it work in a DM or a mention
- 4Connect a repository when you want code
- 5Watch every step in the portal