AI 幾分鐘即可建立儀錶板,OnePage 如何管理生成後的 HTML?
AI Can Build a Dashboard in Minutes. What Happens Next?
OnePage 是開源、自託管的 HTML 頁面發布及管理平台,讓 AI 生成的儀錶板可透過專屬連結分享,並支援存取控制、版本記錄、發布更新及回復舊版本。平台採用 FastAPI、SQLite 和 Docker 部署,亦可在沒有互聯網的環境運作,且不限定 AI 供應商。項目另提供 Excel 報告工具,包括在瀏覽器本機處理檔案的匿名化功能。
AI Can Build a Dashboard in Minutes. What Happens Next?
AI has changed how quickly we can build things.
Ask Claude, ChatGPT, or another AI coding assistant to create a dashboard, and within minutes you can have a surprisingly polished HTML report.
Charts, filters, tables, interactive controls, custom layouts — sometimes all in a single file.
But there is a problem nobody talks about enough.
What happens after the AI generates the HTML?
The missing piece between generation and actual use
Imagine this workflow:
- You ask an AI assistant to analyze an Excel workbook.
- It generates a beautiful interactive HTML dashboard.
- You send the file to a colleague.
- They forward it to someone else.
- Someone makes a correction.
- Now there are several versions of the same report.
Which one is the latest? Who has access? Where is the source of truth?
This is not really a problem with AI. It is a problem with everything that happens after AI finishes its work.
We've become very good at generating content. But publishing, sharing, maintaining and governing that content is still surprisingly fragmented.
I started building OnePage to solve this
OnePage is an open-source, self-hosted platform for publishing and managing HTML pages.
The idea is simple: instead of treating every generated HTML file as an attachment, treat it as a small internal application.
Upload an HTML file, and OnePage gives it:
- Its own URL.
- Access control.
- Version history.
- The ability to publish updates.
- The ability to roll back to previous versions.
- A way to download the page as a standalone HTML file.
The goal is to make AI-generated reports easier to share and maintain, without turning every simple dashboard into a separate software project.
Why self-hosted?
For many organizations, sending internal reports to external services is not an option.
OnePage is designed to run on your own infrastructure.
The stack includes FastAPI and SQLite, with Docker-based deployment. It can also operate in environments without internet access.
Importantly, OnePage does not require you to use a particular AI provider.
You can generate HTML using Claude, ChatGPT, Qwen, DeepSeek, or your own tools, and then publish the result through OnePage.
The AI generation process and the publishing layer remain separate.
I think this separation is important: organizations should be able to choose their AI tools without having to change how they distribute and manage the results.
Beyond HTML publishing
The project also includes tools for working with Excel-based reporting:
- Browser-based report generation.
- Data quality checks.
- Spreadsheet anonymization.
- Interactive data exploration.
The Excel workflows have different data-handling characteristics, so it is important to distinguish them.
For example, the anonymization tool processes files locally in the browser. Some report-generation workflows can publish processed data and supporting information to the OnePage server.
This distinction matters, especially in enterprise environments.
Try it yourself
OnePage is open source and available under the Apache 2.0 license.
GitHub repository:
https://github.com/onepage-bi/onepage
You can clone the repository and follow the setup instructions in the README to run it locally using Docker.
I'd encourage you to explore the demo and see whether the publishing workflow makes sense for your use case.
What I'm trying to figure out
This is still an early-stage project. It has been used in a production environment, but I'm looking for independent users and developers who are willing to experiment with it.
There are a few questions I'd genuinely like to discuss:
- Are AI-generated HTML dashboards becoming part of your everyday workflow?
- How do you currently share and maintain these reports inside your organization?
- Would you use a self-hosted publishing layer for this purpose?
- What would make a tool like this genuinely useful to your team?
I'm particularly interested in feedback from people working with Python, BI, data engineering, self-hosted infrastructure and local AI.
I'm building OnePage in the open, and constructive criticism is very welcome.
GitHub: https://github.com/onepage-bi/onepage
Thanks for reading!
來源:DEV Community · dev.to
