Stacker vs Kubernetes

Stacker builds internal tools and customer portals on top of existing data. From late October 2025 the entire changelog is one project: an AI Builder Agent that generates and edits apps by conversation. In under seven weeks it went from generating initial pages and layouts to editing tables and fields, creating lookups, rollups and formulas, reshaping create forms, reordering navigation, building white-labelled external portals with custom domains and permissions, and finally taking a spreadsheet upload and configuring a schema and matching layouts from it.

The sequencing is deliberate: each release hands the agent one more thing that previously required the no-code editor, while the company repeatedly reassures users that the full editor still works on AI-built apps. That dual framing — build by conversation, refine by hand — is the position Stacker is defending, and it is a reasonable answer to pure prompt-to-app tools that leave nothing to adjust afterwards. The portal release is the notable widening, since it points the agent at the external-user product rather than internal tools.

Every surface except data connection has now been handed to the agent; connecting and mapping an external source — the step still done manually before any of this works — is the remaining gap, and the spreadsheet uploader is the first move toward closing it.