Thanks!
On our homepage (https://davia.ai/showcase) we already showcase examples like AI SDK, E2B, GPT OSS, and Transformers. We’ll also add more examples directly on our GitHub soon.
Exactly. The wiki is editable so AI gives a first draft, and developers refine it. Some companies are fine with vendor APIs, but we’ll add local model support for full privacy.
If you’ve ever tried making a Notion page do more than just hold text, embeds, or basic databases — like building a public form, a mini dashboard, or something where parts of the page act like real apps — you’ve probably run into friction.
Maybe you felt stuck with weird hacks, duplications, or components that barely talk to each other.
The big deal isn’t that Notion can’t do stuff; the deal is what you have to do to get there. And that’s where the trade-offs start to show.
I’ve lived in Notion for years, but I keep hitting the same ceiling: Notion was built for people, not for AI. Because it's closed, agents like Cursor can’t write to it and bulk edits stay manual. I fall back to local markdown I edit with Cursor, but that breaks as soon as we need shared tables or quick productivity tools.
We’re working on something more open:
- Docs and tables live as plain code you (and AI) can edit
- Any AI agent like Cursor or Claude code can propose changes without fighting a closed UI.
- A web editor is still available for quick comments when needed.
With Davia, you build on FastAPI and React best practices.
Streamlit and Gradio rely on fixed components, which makes it hard to adapt the UI to your specific use case. Davia lets you define any interface you need.
Streamlit also has production limitations like authentication, layout control, and API integration. And for AI use cases, it reruns the whole script on every input, making state management difficult. Davia supports real-time streaming and proper stateful interactions.
The use of a single POST request (the underlying logic behind the @app.task decorator) is meant to simplify things, especially for users who aren’t familiar with FastAPI. It abstracts away routing and request handling so you can focus on writing business logic without worrying about HTTP methods, URL paths, or response formatting.
That said, since Davia is built on top of FastAPI, you can absolutely define and use your own endpoints if you prefer.