Skip to content

Roadmap

Wallabi is in early beta. The core workflow — connecting to your data, building apps, and deploying them — is working well. Here’s where we’re headed.

We’re sharing this openly because we want your input. If something here matters to you, or if something’s missing, let us know.

Today, building a data app means setting up a local development environment. That works — but it shouldn’t be required. We’re working toward a browser-first experience where you can plan, build, and deploy apps entirely from the Wallabi app or a conversation with Claude Code. Describe what you want, preview it live, and ship — no local setup needed.

Beyond building, we’re investing in the full lifecycle: planning tools to help you decide what to build, guided sessions for building it, and management tools for keeping your apps up to date once they’re deployed — platform updates and maintenance applied automatically, without manual effort.

Wallabi already connects to major databases and SaaS tools. We’re expanding the list of supported sources, improving the data exploration experience, and making it easier to understand your data before you start building.

Right now, Wallabi is focused on reading data — great for dashboards and analytical experiences. We’re exploring the ability for data apps to write back to your systems: updating records, triggering workflows, and integrating with transactional tools. This opens up use cases beyond analytics — approvals, data entry, operational tools.

Data apps today show data when you open them. We want to support event-driven patterns: background processing, scheduled data refreshes, and alerts. Think: a notification when a key metric changes, or a data pipeline that keeps your app current automatically.

Apps currently run on Wallabi-managed infrastructure. We’re exploring options for organizations that need to host on their own systems.


Have thoughts on any of this? We’d love to hear from you — drop us a note.