Ask HN: Selling software to company I work for as an employee
Ask HN: Places in the UK / Europe Related to computers
Show HN: Web Apps for Python Devs with Auto-Generated UI
We’re Afnan, Theo and Ruben. We’re all ML engineers or data scientists, and we kept running into the same thing: we’d write useful Python functions, either for ourselves or internal tools, and then hit a wall when we wanted to share them as actual apps.
We tried Streamlit and Gradio. They’re great to get something up quickly. But as soon as we needed more flexibility or something more polished, there wasn’t really a path forward. Rebuilding the frontend properly in React isn’t where we bring the most value.
So we started building Davia. You keep your code in Python, decorate the functions you want to expose, and Davia starts a FastAPI server on your localhost. It opens a window connected to your localhost where you describe the interface with a prompt. It then builds the interface, and you can deploy everything in one step. Think of it as Lovable, but for Python developers.
It works especially well for building AI tools. We built it to integrate tightly with LangGraph, so if you’re writing agents or workflows, you can turn them into real apps without leaving Python.
Docs and examples here: https://docs.davia.ai GitHub: https://github.com/davia-ai/davia
We’re still in early stages and would love feedback from others building internal tools or AI apps in Python.
1. Why does it use two requests with OPTIONS and POST methods instead of a single GET? Is this to reduce the amount/complexity of error handling logic in the generated application?
2. Why use a POST http request to get the sales data. I would have expected the route to use GET in this situation?