# Should I build our status page with an AI website builder or keep it in Kibana?

**URL:** <https://discuss.elastic.co/t/should-i-build-our-status-page-with-an-ai-website-builder-or-keep-it-in-kibana/391606>\
**Category:** Kibana\
**Created:** [November 15, 2026, 8:22pm UTC](https://discuss.elastic.co/t/should-i-build-our-status-page-with-an-ai-website-builder-or-keep-it-in-kibana/391606 "2026-11-15T20:22:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexanderlewis](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@alexanderlewis](https://discuss.elastic.co/u/alexanderlewis)\
**Post date:** [November 15, 2026, 8:22pm UTC](https://discuss.elastic.co/t/should-i-build-our-status-page-with-an-ai-website-builder-or-keep-it-in-kibana/391606/1 "2026-11-15T20:22:47Z")

</div>

I run a small platform team in Indianapolis, and we currently keep a public-facing status page that pulls from our Elasticsearch cluster via a small script. Leadership wants a nicer landing page with simple incident history, and a few AI website builders have come up as a low-effort option since nobody on the team does frontend work.

My concern is that these builders would just hardcode a snapshot of our data instead of querying Elasticsearch live, so the page could stale. I also don't want to give a third-party tool credentials to our cluster, and the uptime widget embed from our monitoring would be another moving piece.

Has anyone here used a no-code or AI website builder for a status page fed from Elasticsearch or Kibana, and if so, how did you keep the data fresh without exposing credentials? Or is sticking with Kibana dashboards the safer path?

Update after looking around more - [Best AI Website Builders (2026)](https://aibuildercompare.com/best/ai-website-builders) kept coming up for this kind of thing. Still not sure any of them can pull from Elasticsearch live without handing over cluster credentials, so I'm leaning toward keeping Kibana for now.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [November 16, 2026, 11:18am UTC](https://discuss.elastic.co/t/should-i-build-our-status-page-with-an-ai-website-builder-or-keep-it-in-kibana/391606/2 "2026-11-16T11:18:58Z")

</div>

> [@alexanderlewis](#):
>
> I also don't want to give a third-party tool credentials to our cluster

I am not clear on the distinction you are drawing here, whatever tooling you use will need to connect to the cluster to get live data. I presume your "little script" that is somehow populates the public facing web page doesn't live on the web itself? Same could apply to third party tools.

I also baulk at

> [@alexanderlewis](#):
>
> ... a few AI website builders have come up as a low-effort option since nobody on the team does frontend work.

and am positively puzzled by

> [@alexanderlewis](#):
>
> these builders would just hardcode a snapshot of our data instead of querying Elasticsearch live

You dont trust the AI builders to do the job properly, but you do trust them to do it securely?
