Hey there! So it’ll be a Python-first PaaS focused on running data apps. So it’ll include storage for pickle files, a simple NoSQL database, identity aware proxy so you can configure specific routes as being authenticated, secrets manager, and the ability to run background jobs on a schedule (usually some sort of ETL process or model training).

I go back and forth on the REPL. We built a REPL but then a lot of the beta users preferred the power of GitHub Codespaces so right now I’m thinking that no, it’ll not contain the REPL.

If you have a use case, would you like to beta test the hosting?

Oh, that could be fun. I’ll give it a spin.

I’m working on a something like a structured-data first wiki. Most users will be unauthenticated read-only, served well by a static site. A smaller population will submit new data and edits. Submitted data will need some processing pipelines.

I’m using Dolt/Dolthub to publish high fidelity data dumps. I’ve been leaning towards doing a static site built directly from Dolthub queries, then use an offline workflow for modifying data. However if I can bring those together easily into something more like a standard dynamic site, that would be useful.

For example, I could use your native data storage for basic user profile and authentication information, like API keys for Dolthub.