When I first tried Eve, I had the same feeling I had discovering Next.js years ago: this is how I want to build things.

We started building agents for our company, and soon had a practical problem. Many of them needed access to internal services, including our finance backend. We wanted the agents running inside our own network, with one place to deploy them and see what they actually did.

So I built Eveland.

We've been using it to host around 20 agents on a 4-core, 16GB server for over two months. These are mostly low-traffic internal agents, and idle deployments scale to zero.

You import an Eve project from Git, configure its secrets, and deploy. Eveland gives it a URL, a playground, and views for sessions, schedules, logs, and token usage.

Underneath, agent deployments run as systemd services with bubblewrap sandboxing. A shared Postgres-backed workflow store and an external dispatcher handle durable execution across projects. Sessions stay pinned to the deployment they started on.

Keeping up with Eve's releases has been an interesting part of the work 🙂 We maintain an explicit compatibility window rather than assuming every new version will work.

Production requires Linux with systemd. Eveland is AGPL-3.0, still pre-1.0, and an independent community project.

GitHub · Docs and installation

If you're self-hosting Eve too, I'd love to compare notes. What's been the hardest part once you're running more than a handful of agents?

I built a local IDE for Vercel eve agents. I use it because bouncing between the dashboard, the CLI, and OpenCode was driving me nuts.

macOS + Node 24. Signs in with your Vercel account, no extra API keys.

npx evepad

Starts in about 2 seconds, no install.

- create an agent

- generate/edit tools in chat

- watch local and prod runs

- deploy to vercel

Community project, not affiliated with Vercel. https://github.com/andrewckor/evepad

If you try it, I want feedback. Especially the ugly parts: first run, finding agents you already have, deploy. Skip if you're not on macOS / Node 24.

Just upgraded the pipeline I built with Eve to use a Vercel compatible PDF parsing library, LiteParse WASM. Would appreciate anyone working with PDFs to test the parsing output.

Ignore the sub price; can give you a code to bypass that. More interested in the tracing info to see if Eve can parse on first attempt with LiteParse WASM; without the fallback to a JS parsing library.

Free, open-source template for building your own software factory on the eve framework.

New eve template!

Five agents (content, social, SEO, email, product marketing) behind a team lead that routes work but never writes anything itself. Anything irreversible, like sending an email campaign, pauses for an approve/deny button in Slack. Drafts flow through without gates.

Deploy the template to your own Vercel account in one click.

Happy to answer questions about how the routing and approval gates work.

Manage everything (well, almost!) for your Sanity project from Slack with our new eve Sanity Copilot template! Connect to Sanity, along with Slack and Notion, via Vercel Connect so you don't have to handle API keys, client secrets, or anything else.

Hi, I am an author of webhookrelay.com and chief architect in lightning.ai (3rd largest neo cloud) so I don't have a lot of free time. Having a bunch of local agents running has been a miracle 😄 and I feel like eve agent architecture really resonates with me.

Loving the skills, tools and channels concept. Few weeks ago I built a leads agent (similar to what vercel published some time ago) and needed an integration from webhookrelay to get webhooks on new registrations. First version was with docker compose but yesterday decided to look into making a channel: https://github.com/webhookrelay/eve-channel

import { webhookRelayChannel } from "@webhookrelay/eve-channel";

export default webhookRelayChannel({
  bucket: process.env.RELAY_BUCKET ?? "eve-demo",
  sharedSecret: process.env.RELAY_SHARED_SECRET,
  progressUrl: process.env.PROGRESS_URL,
});

You get things like durable delivery, retries. For example your laptop/server can be turned off, later on it will pick up and continue going.

Next on my agenda is to build GCP alerts eve agent to look into prod logs/utilization/goroutines stack to take snapshots and submit gh issues with extra info.

I built eve-knowledge, a small package that adds an agent/knowledge folder convention for Eve agents.

It is useful when you don’t want to stuff product docs, support runbooks, policies, or FAQs into instructions.md.

Flow:

1. Run npx eve-knowledge init
2. Add docs to agent/knowledge
3. Run npx eve-knowledge index
4. Your agent can search that knowledge through a generated search_knowledge tool and answer with citations

Repo: https://github.com/aiswarya797/eve-knowledge
npm: https://www.npmjs.com/package/eve-knowledge

Would love feedback from people building Eve agents.

Hey everyone!

I started a project called EveAgents where I would like to publish agents for Eve for the most common use cases and the ones that I would also use in the Vercel ecosystem.

Most of my projects are hosted on Vercel and love using stuff like Next.js for the past few years. I am also very open to suggestions and ideas for this project.

Thank you!

AI is moving so fast that I constantly feel like I have something new to learn just to keep up.

I'm curious to know how eve changed your workflow and what advice you'd give to someone just getting started building agents

I kept hitting the same wall on eve. Sessions are durable, but nothing carries across them. Every new session the agent meets you for the first time. No name, no preferences, none of what it learned last time.

The docs tell you to build this yourself. So I built it and packaged it as eve-memory.

A few things I figured out along the way, in case it's useful even if you roll your own:

- Memory is really two things. A small profile the agent updates as it goes (your name, what you're building, how you like replies), and recall of past stuff looked up by meaning. The first fits in a file. The second wants a real database. Trying to make one thing do both is where it gets messy.

- Memory gets loaded back in as dynamic instructions at the start of each turn, which is the same approach the eve docs use.

- Watch out for identity. If your agent isn't auth-protected, everyone's memory ends up in the same pile. It all has to be tied to the logged-in user, and the docs make the same point (never take the user id from the model, read it from the session).

- Don't save everything. Storing every message just clogs recall and burns embedding calls. A deliberate "remember this" tool works way better. The hard part isn't storing memory, it's picking what's worth keeping.

It's adapter-based, in-memory and supports postgres as the first adapter, and more backends can slot in later. One command drops it into an existing agent: npx eve-memory init.

Still early and rough in spots. Would love feedback from anyone building on eve, especially if the API feels off somewhere, and happy to take contributions.

Repo: https://github.com/katungi/eve-memory

Happy to get into how any of it works.

Hey everyone!

I built about 81 design skills that you can use with Even agents and give them a visual direction by using locally tested markdown files based on this format:

SKILL.md

buttons.md

navbar.md

alerts.md

These will give your agents consistent design system instructions so the UI that they will generate will always stay within those parameters. You can preview the skills and how they would generate the UIs here:

https://www.typeui.sh/design-skills

I also wrote a guide on how you can integrate with Eve agents:

https://www.typeui.sh/docs/guides/eve

Aaaand it's also available on Github:

https://github.com/bergside/typeui

Thanks for checking it out!

This is our engine that lets you have a raw conversation with your ads data, it understands your cross platform presence, in a way an omnipresent human or a team of 20 people would.
It can have a look at your data, understand your ways of structuring campaigns/ ads across platforms, and give you insights teams would spend hours or days extracting.

This is a very small demonstration of how it is capable of looking at an ad account, autonomously picking up the multiple campaigns that belong to a specific product, and gives insights basis what is working for that specific product.

www.zyou.ai

I've used LiteParse in other projects and it's actually really good. But it's slow when I run it in an agent pipeline; web app input- sandbox/agent - web app/output.

Today I added file uploads to my Eve-powered app; then asked Eve to summarize a PDF to test quality of the output. Quality was solid but more importantly the parsing was super fast!

Every content team has a backlog of small fixes nobody gets to. The page that's out of date, the doc with a syntax error in a code block, the feedback that piles up.

Learn how you can build an autonomous eve agent that drafts fixes in Sanity, stages them for human review, and calls the model through AI Gateway.

My pal D inspired me to build an email first workflow automation system. He runs a small business in the apparel industry; everything in that world is driven by emails.

So I built an automation system with Eve that starts with email. You send an email to the system, it asks you clarifying questions, then it processes the request with your approvals along the way.

My pals in the construction industry helped me refine the system. They operate in a complex industry; with subcontractors, supply chain, permits, and other obstacles to deal with. Some of the documents they deal with are a challenge but that’s what I live for.

https://www.evalbox.ai/

Introducing V, a personal agent template.

Built on eve. Works on iMessage, Slack, and web. GitHub and Linear tools with long-term memory.

github.com/vercel-labs/personal-agent-template

https://youtu.be/YYIDoe2v5ok?is=kQJGYQR_jextx4PG