Intent-Oriented Programming Runtime

EVOID

Your data declares what it needs.
The runtime handles how.

Built for Modern Backends

A runtime that adapts to your data, not the other way around. Write handlers, declare intents, let EVOID handle infrastructure.

Intent-Driven

Your data model carries infrastructure intent. The runtime resolves it automatically.

Async-Native

Built on Python 3.13+ with full async/await. Every processor runs without blocking.

Plugin-Based

Schema, storage, cache — every engine is a swappable plugin.

Parallel Execution

Run multiple intents concurrently with built-in gather and priority queues.

Microservices

Project + Service structure with inter-service message bus communication.

Multi-Adapter

Same logic, different interfaces — ASGI, CLI, Telegram, Robyn, WebSocket.

Two intents. Zero boilerplate.
api.py

Why EVOID Exists

Every API endpoint repeats the same infrastructure decisions. Which database? How to cache? Whether to encrypt? What audit trail?

EVOID lets your data model carry these decisions as intent. The runtime reads it and adapts — automatically. No more boilerplate, no more config files scattered everywhere.

Define your data. Write your handlers. EVOID handles the rest.

@route

Function-based decorators. FastAPI / Flask style. Familiar syntax for quick prototyping.

@controller

Class-based routing. NestJS / Django REST. Organize large APIs cleanly.

Native

Full control with explicit Intent API. No sugar — just the IOP model.

Tutorial

Step-by-step guide from zero to production in 5 minutes.