468 karma · joined July 19, 2015
I've been working on a similar product. Users can select between Streamlit/Shiny: https://editor.ploomber.io/ - so not necessarily for BI (although you can use it for that), but more broadly focused on data apps.
- You cannot extract live variables (needed for testing)
- Cannot use pdb for debugging
- Cannot profile memory usage
You can do all of that with ploomber-engine (https://github.com/ploomber/ploomber-engine).
Disclaimer: I'm the author of this package
I might add a subscribe button once I get some time :)
We already support frameworks like Streamlit, Gradio, Shiny, Solara, Voila, among others. Ping me if you're interested!
We added support recently and have some nice features like password protection: https://docs.cloud.ploomber.io/en/latest/apps/quarto.html
I've just deployed an app to Ploomber Cloud: https://dry-fire-8233.ploomberapp.io/
Docs: https://docs.cloud.ploomber.io/en/latest/apps/shiny-express....
We (Ploomber) have been working with the team to help their community easily deploy applications in our cloud platform: https://docs.cloud.ploomber.io/en/latest/apps/solara.html
We recently worked with the chDB team to add support for Jupyter notebooks: https://jupysql.ploomber.io/en/latest/integrations/chdb.html
Job openings: https://www.workatastartup.com/companies/ploomber
Ploomber is hiring engineers to build a platform to deploy AI applications.
We're well-funded (raised a seed round last year) and have thousands of weekly active users in our open-source projects (https://github.com/ploomber/)
And you can run Jupyter notebooks from the CLI with Ploomber: https://github.com/ploomber/ploomber
A few months ago, we worked with the team to bring Hydra to Jupyter, you can check out the tutorial here: https://docs.hydra.so/analyze/jupyter
JupySQL's GitHub: https://github.com/ploomber/jupysql
Most of my notebooks are a mix of SQL and Python: SQL for most processing, dump the results as a pandas dataframe (via https://github.com/ploomber/jupysql) and then use Python for operations that are difficult to express with SQL (or that I don't know how to do it), so I end up with 80% SQL, 20% Python.
Unsure if this is the best workflow but it's the most efficient one I've come up with.
Disclaimer: my team develops JupySQL.
If you use notebooks: my team is working on JupySQL, a tool to improve the SQL experience in Jupyter. https://github.com/ploomber/jupysql
Disclaimer: My company develops JupySQL