# Fluxzero > Fluxzero is the European application cloud for people and AI agents building, running, and scaling real software. ## Core pages - [Fluxzero — The European cloud for AI-built apps](https://fluxzero.io/): Fluxzero is the European application cloud for people and AI agents building, running, and scaling real software. - [Inside Fluxzero — The application cloud](https://fluxzero.io/how-it-works/): See how Fluxzero keeps infrastructure out of your application so people and AI agents can focus on building the product. - [Fluxzero Pricing — Build free. Launch, then run.](https://fluxzero.io/pricing/): Fluxzero pricing for builders: build locally for free, put your app online with Starter, then run with Startup, Scale Up, or Enterprise. - [About Fluxzero - Origin story](https://fluxzero.io/about/): The origin story behind Fluxzero: why we made a production-ready foundation available to builders using AI. - [Start building with Fluxzero](https://fluxzero.io/get-started/): Connect Fluxzero to your coding agent and start building your product. - [Contact Fluxzero](https://fluxzero.io/contact/): Contact Fluxzero for launch access, pricing questions, partnerships, and product feedback. --- # Fluxzero — The European cloud for AI-built apps Source: https://fluxzero.io/ ## The European cloud for AI-built apps The all-in-one cloud with frontend, backend, data, security, deployment, and observability working as one. [Get started →](https://fluxzero.io/get-started) [Talk to us](https://fluxzero.io/contact#contactForm) 100% EU-operated · Built on ISO 27001-certified and SOC 2 Type 2-audited infrastructure. ### The cloud for anyone AI lets anyone build products. Fluxzero gives every product a reliable backend from the first prompt. ##### Ship without an engineering team Build and launch serious products without assembling a backend or platform team. ##### Build with peace of mind Security, reliability, and recovery are built in from day one, not left for you or your agent to get right. ##### Scale without replatforming The same application model works locally and at full scale, so growth does not force a new architecture. ### Other clouds run infrastructure. Fluxzero runs your product. Infrastructure clouds leave you responsible for the tech stack. With Fluxzero, your only responsibility is the product. | Comparison category | Supabase + Vercel — Database platform + frontend cloud | Railway — Application infrastructure | Fluxzero — The product cloud | | --- | --- | --- | --- | | Built for | Developers | Developers | Anyone building with AI | | What you set up | Database, frontend hosting, permissions & integrations | Services, databases, networking, load balancing & deployment | No infrastructure setup | | What the cloud handles | Auth, database & frontend hosting | Deployments, networking & databases | Everything your product needs to run | | When you add a feature | Build the feature across every application layer | Build the feature across services and infrastructure | Define what the feature does | | Security & recovery | Database backups; application recovery is left to you | Left for you to build into the application | Handled by the cloud | | Path to scale | Requires rearchitecting or replatforming | Requires rearchitecting or replatforming | Scale without rebuilding | | Based in | Singapore + United States | United States | European Union | [Explore how Fluxzero works →](https://fluxzero.io/how-it-works) No technical noise ### AI works better when there’s less to think about When AI does not have to integrate cloud infrastructure, it can stay focused on the product behavior you actually care about. ##### Spend fewer tokens Spend your prompt budget on product behavior, features, and user experience. ##### Less risk Infrastructure is no longer your AI agent’s responsibility. ##### 100% product context The tech stack no longer consumes your agent’s context, so every prompt can stay focused on the product. Built to scale ### Start small. Scale as your product grows. The same foundation supports early products and high-throughput systems with complex business logic. - **GB / min production throughput:** 100+ About 700,000 tweets every second, nearly 5 times X.com’s record. [*](https://fluxzero.io/#tweet-throughput-note) - **resolved requests / sec:** 1M+ Commands and results, end to end across applications. - **less application code:** up to 99% Across legacy migrations with the same behavior. * Estimate based on a [2.3 kB average serialized tweet size](https://www.research-collection.ethz.ch/bitstreams/77b38ad3-f165-4bda-9fca-6a1d13913836/download) and [X.com’s published record of 143,199 tweets per second](https://blog.x.com/engineering/en_us/a/2013/new-tweets-per-second-record-and-how). ### Frequently asked questions #### What is Fluxzero? Fluxzero is a cloud platform for applications built with AI. It hosts your frontend and backend, stores your data, and runs the application in production. Unlike other clouds, Fluxzero gives every product a reliable backend, so your agent can focus on the product instead of its tech stack. #### Can I really launch serious software with Fluxzero? Yes. Fluxzero is built for products where reliability matters: products with valuable data, complex workflows, permissions, integrations, and business rules. You and your coding agent build the product behavior. Fluxzero takes responsibility for the technical foundation underneath your product, including security, reliable message delivery, recovery, auditability, and scale. The same hardened foundation supports early-stage products and high-throughput enterprise workloads, so you can launch without hiring backend engineers and keep the same backend as your product grows. #### My agent can generate a backend. Why should it use Fluxzero? An agent can generate a backend quickly. But building your product is a different job from building a hardened backend. Your agent is focused on the product. The backend it generates becomes a codebase you must keep secure, reliable, understandable, and ready to scale as the product evolves. Every shortcut taken to launch becomes something you own. Fluxzero gives your product a hardened backend foundation built and operated by experienced backend engineers for demanding enterprise workloads. Because products run on a shared platform foundation, improvements to security, reliability, recovery, and scale compound and benefit every product, without adding infrastructure code to your application. Your codebase stays focused on the product. As usage and complexity increase, you keep building on the same foundation instead of rebuilding or replatforming. #### How is Fluxzero different from Supabase + Vercel, Railway, or other clouds? Those clouds give you infrastructure and services that still need to be selected, connected, secured, scaled, and operated. You or your agent remains responsible for turning them into one reliable product. Fluxzero provides and operates that application foundation as one cloud, so you can focus on the product instead of operating the platform underneath it. If you prefer to design, tune, and operate every infrastructure layer yourself, a component cloud may suit you better. #### What does building with Fluxzero look like? Start by copying one instruction into your coding agent. This is the easiest way to build with Fluxzero. The application your agent helps you build is real code that developers can inspect, test, and extend from their own IDE. When the product is ready, the same application can be deployed to Fluxzero Cloud. #### What kinds of products can I build? Any application can run on Fluxzero, across product domains and workload sizes. That includes SaaS products, marketplaces, portals, internal tools, consumer apps, and AI-enabled software. #### What kinds of companies run on Fluxzero? Fluxzero is trusted in production across product domains and workload sizes, from single-founder companies and scale-ups to enterprises such as the organization behind the digital infrastructure of Europe's largest port. #### Will I outgrow Fluxzero or need to rebuild later? No. The same application works locally and at production scale. Individual workloads can receive more capacity as your product grows, without forcing the whole product onto a new architecture. If developers join later, they work in a real codebase, not a generated black box. They can inspect, test, and extend the product in their own IDE while Fluxzero continues to run the foundation. #### Do I lose visibility by trusting my backend to Fluxzero? No. Fluxzero is not a black box. It works more like an X-ray of your product: you can see its messages, web requests, application logs, errors, and the user or system behind each interaction. Every interaction is part of a searchable audit trail. Correlation and tracing let you follow a single request across applications or zoom out to find patterns, performance issues, and failures across the whole product. #### Do I own my code and data? Yes. Your application code and product data remain yours. The code does not depend on proprietary Fluxzero annotations, and your data can be exported in a machine-readable format. #### When do I start paying? Building and running locally is free. You start paying when you activate a plan to put your product online. Still wondering? [Get in touch](https://fluxzero.io/contact) and we'll help. ### Launch what used to require an entire engineering team. [Get started →](https://fluxzero.io/get-started) [Talk to us](https://fluxzero.io/contact#contactForm) --- # Inside Fluxzero — The application cloud Source: https://fluxzero.io/how-it-works/ ## AI lets anyone build products. Time for the cloud to catch up. Fluxzero is the cloud for this new generation of builders. You decide what to build. Your agent builds it. Fluxzero makes it run. [Get started](https://fluxzero.io/get-started) [Read the technical docs](https://fluxzero.io/docs) ### More products should not mean more infrastructure. Traditional clouds were designed for engineering teams building and operating one product at a time. As AI creates more products, duplicating the same backend for each one no longer makes sense. #### Product 1 - Unique product logic - Services & workers - Persistence - Messaging & recovery - Gateways & proxies - Load balancing - Security & discovery - Observability - Deployment #### Product 2 - Unique product logic - Services & workers - Persistence - Messaging & recovery - Gateways & proxies - Load balancing - Security & discovery - Observability - Deployment #### Product 3 - Unique product logic - Services & workers - Persistence - Messaging & recovery - Gateways & proxies - Load balancing - Security & discovery - Observability - Deployment #### Product N - Unique product logic - Services & workers - Persistence - Messaging & recovery - Gateways & proxies - Load balancing - Security & discovery - Observability - Deployment ### Your product should be the whole application. Traditional applications mix product features with the technical work needed to run them. With Fluxzero, the application contains only what makes the product unique. The cloud handles the rest. **Inside a traditional application** Everything below ships as part of the app - Product behavior - Service wiring and orchestration - Integration adapters - Persistence code and schemas - Retry and recovery paths - Ingress and service networking - Observability plumbing - Deployment topology **Fluxzero application** **Product behavior** **fluxzero cloud** - State & history - Message delivery - Search - Policy enforcement - Replay & recovery - Observability - Runtime routing - Deployment & scale ### Everything your product needs to run. Built into Fluxzero, instead of assembled separately for every product. #### Model State / history / relationships / search #### Interaction Commands / events / queries / HTTP & WebSocket / schedules #### Policy Validation / authorization / invariants / data protection #### Cloud Cross-app routing / ordering / concurrency / recovery / observability / scale ### Let your agent build the product. Fluxzero keeps infrastructure out of the application, so your agent can focus on what the product should do. #### The product stays visible The application describes the product in its own terms, not through technical layers. #### A complete history Every interaction keeps its context, so you can trace what caused a problem. #### Fix and replay After a fix, affected work can be replayed without rebuilding the application around it. #### Test the behavior Your agent can prove what a change does without setting up infrastructure first. ### The code describes the product. Your product’s behavior stays visible in the application. Fluxzero keeps the infrastructure out of the way. [Read the technical docs](https://fluxzero.io/docs) **ProjectTasks** Java ```java @Model record Project( @EntityId ProjectId projectId, String name) {} @Model record Task( @EntityId TaskId taskId, @Parent(pathInParent = "tasks") ProjectId projectId, String title, @With boolean completed) {} record CompleteTask(TaskId taskId) { @AssertLegal void assertOpen(Task task) { if (task.completed()) { throw TaskErrors.alreadyCompleted; } } @Apply Task apply(Task task) { return task.withCompleted(true); } } ``` **CompleteTaskTest** Test ```java @Test void completeEmitsEvent() { testFixture.givenCommands( "create-project.json", "create-task.json") .whenCommand( "complete-task.json") .expectEvents( "complete-task.json"); } ``` ### See what your application is responsible for. With other clouds, your application includes the product and the infrastructure around it. With Fluxzero, it contains only the product. | Responsibility | Other clouds — Supabase + Vercel, Railway and similar clouds | Fluxzero — The product cloud | | --- | --- | --- | | Application architecture | Product behavior plus services, adapters and infrastructure architecture | Product behavior only | | State and history | You design schemas, queries and transaction boundaries; state is stored as current snapshots unless you build history | Model state, relationships and complete history are built in | | Coordination | App code owns routing, concurrency, ordering and cross-service coordination | The cloud routes, orders and coordinates every interaction | | Failure and recovery | You build retries and recovery paths; crashes can still lose in-flight work | Durable delivery, replay and recovery are built into the cloud | | Ingress and networking | You assemble and secure gateways, proxies, service networking and discovery | One secured application boundary, handled by the cloud | | Scale and operations | Configure, connect, scale, monitor and operate every component and service | Distribution, backpressure, observability and scale are automatic | ### Fluxzero improves. Every product benefits. Every improvement to Fluxzero reaches your product automatically. You do not have to rebuild or migrate it. **fluxzero** Shared cloud runtime Continuously improved - Performance - Hardening - Operational insight - Recovery Inherited automatically Every product ### When to choose Fluxzero. Choose Fluxzero when you want to build the product, not the platform required to run it. #### Fluxzero For builders who want to focus on product features and expect the technology underneath to just work. #### A component cloud For engineering teams that want full control over how their infrastructure is designed and operated, from service topology to capacity planning and failure recovery. ### Build what matters. Let the cloud carry the rest. [Get started](https://fluxzero.io/get-started) [Explore the technical model](https://fluxzero.io/docs) --- # Fluxzero Pricing — Build free. Launch, then run. Source: https://fluxzero.io/pricing/ Fluxzero pricing ## Choose your plan Build your entire app for free, then launch it in production. Scale your product as you grow, without changing foundations. Free #### Builder € **0** Build your entire app before you pay. [Get started](https://fluxzero.io/get-started) - Use Claude Code, Codex or other agent - **Local runtime** - Local logs - Community support Launch #### Starter € **49** per week or €190 per month Start running in production. [Request launch access](https://fluxzero.io/contact) - Includes a fully-featured environment: - **Starter cluster included** - **Starter app included** - 100GB storage included - Auth included (max 100 users) - 1 custom domain - Audit trail - Slack support Grow #### Startup € **490** per month For products gaining traction. [Request startup plan](https://fluxzero.io/contact) - **Small cluster included** - **2 small apps included** - 200GB storage included [1] - 1000 users included - 7 days backup [1] - Unlimited domains - Audit trail - Ticket support Scale #### Scale Up € **890** per month For products that need more capacity. [Request scale up plan](https://fluxzero.io/contact) - **Medium cluster included** - **2 medium apps included** - Unlimited clusters & apps [1] - 400GB storage included [1] - Unlimited users included - Unlimited backups [1] - Unlimited domains - SSO - 99.9% uptime target - Optional static IPs - Audit trail & insights - Priority support Calculate extra capacity Customize #### Enterprise **Custom** pricing Dedicated setup for larger teams. [Contact us](https://fluxzero.io/contact) - **Custom workloads** - Additional sizes - Custom storage - Custom backup policy - Custom SLAs - Private Slack channel - Unshared hardware optional - Unlimited domains - Audit trail & insights - 24/7 support [1] Extra clusters, apps, backup storage, and storage above the included amount are measured during the month and settled at month-end. ### Included in every paid plan The limits change by plan, but the production foundation stays the same. #### Hosting & runtime - App and frontend hosting - Secure web gateways - Automatic load balancing - App and frontend scaling #### Data & messaging - Data stores - Search - Durable message logs - Seamless inter-app communication #### Visibility - Searchable audit trails - Request traces - Contextual errors - Full visibility into your apps #### Access & isolation - Auth - Role-based access - Fully isolated app components ### Frequently asked questions #### What are clusters and apps? A cluster is the managed environment your app runs on. An app is one running application inside that environment. Starter capacity gets you online quickly; Scale Up lets you add more clusters and apps when your product needs more room. #### When will I be billed? You can build locally for free. Billing starts when you activate a paid plan for an app. Your billing schedule starts on the day your first payment is made. Starter is billed every 7 days; Startup and Scale Up are billed monthly unless agreed otherwise. Extra or larger clusters and apps, and storage above the included amount, are measured during the month and billed at the end of the month. #### Why can I pay weekly for Starter? The weekly Starter option is there so you can experiment with a real Fluxzero cluster for a short period without committing to a full month. It is not meant as a discounted version of the monthly plan. It gives builders a low-friction way to try a live production foundation, validate an idea, or test launch readiness before choosing a longer-running plan. #### Is sales tax included? Prices are shown excluding sales tax, VAT, and similar taxes unless stated otherwise. Any required tax may be added during billing based on your billing details and local rules. #### What capacity is included, and can I cap my bill? Every paid plan includes fixed cluster, app, and storage capacity as shown on the plan card. That included capacity is part of the plan price. From Scale Up, you decide which extra clusters, apps, storage, or options are added before they affect your bill. Fluxzero is designed to make usage visible before it becomes a surprise. #### Will prices change in the future? Pricing may evolve as Fluxzero grows and the platform changes. If a price change affects an active paid plan, we will communicate it before it applies. #### What happens if I cancel or pause my plan? Your app will stop running on the paid plan after cancellation takes effect. In many cases you can stop runtime capacity when an app is not actively running. If you need to pause while keeping data or configuration, contact support and we will help choose the safest option. #### What happens if my payment fails? We will notify you and give you time to fix the payment method. If payment remains unresolved, paid runtime access may be paused until billing is restored. #### What if I need development, test, or staging environments? Additional clusters for development, test, staging, or preview environments can be added from Scale Up. We can help you choose the right size and setup. #### What if I need more scale or higher availability? Scale Up supports additional clusters and apps and includes a 99.9% uptime target. Enterprise adds custom workloads, additional sizes, private hardware, custom SLAs, and dedicated operational support. Fluxzero currently runs from Europe, with more regions planned. #### What happens if I go over included limits? Extra or larger clusters and apps can be added from Scale Up. These are measured during the month and billed at the end of the month. If your data volume exceeds included storage, additional storage is billed at €0.0048 per GB per day. Our fair use limits are designed to cover typical application traffic for most products. If your application generates unusually high public network traffic, we may temporarily limit traffic, request changes, or move you to a suitable plan. Still wondering? [Get in touch](https://fluxzero.io/contact) and we'll help. --- # About Fluxzero - Origin story Source: https://fluxzero.io/about/ Origin story ## Fluxzero started with a simple frustration. Building software kept drifting away from the product itself. The first time we tried to build a serious product, we thought the hard part would be the idea, the users, and the product itself. Instead, we got buried in everything around it. ### The work around the product kept taking over Again and again, we saw the same thing happen. A team would start with a clear product idea, then slowly disappear into the foundation beneath it: auth, data, architecture, permissions, deployment, operations, monitoring, failures, security, scale. None of that work is optional. It is the work that makes software trustworthy. But it is also the work that turns a product into an infrastructure project before anyone even gets to use it. We did not want another workaround. We wanted the foundation we wished had existed from the start. ### Then AI changed who could build AI made it possible for founders, designers, frontenders, domain experts, and small teams to build working software at a speed that used to be impossible. That is exciting. But it also exposes the same old problem in a sharper way. It makes little sense for AI to rebuild the foundation every time it builds a product. And it's risky too: builders are left trusting technical choices while trying to build the product itself. ### So we made our foundation reusable For years, we built systems where correctness, reliability, testing, operations, and scale mattered from day one. Fluxzero grew out of that work. Our obsession is simple: build a best-in-class backend foundation, and keep it out of the product layer so it never slows builders down. What this means now ### Every builder can start on a real foundation Fluxzero gives anyone building with AI a production-ready backend from the start. You focus on the product. Fluxzero handles the architecture underneath, so what you build can become real software. [Get started →](https://fluxzero.io/get-started) --- # Start building with Fluxzero Source: https://fluxzero.io/get-started/ ## Start building with Fluxzero. Just copy this into your agent. ``` Build my app with Fluxzero. Start at plugins.fluxzero.io ``` Works with - [Claude Code](https://claude.com/product/claude-code) - [Codex](https://openai.com/codex/) - [Cursor](https://cursor.com/) - [Gemini CLI](https://github.com/google-gemini/gemini-cli) - [GitHub Copilot](https://github.com/features/copilot) --- # Contact Fluxzero Source: https://fluxzero.io/contact/ Contact ## Get in touch Questions about Fluxzero, pricing, partnerships, or something else? We’d love to hear from you. ### Send us a note A few lines are enough. We’ll take it from there. Full name Email address Message Send Office Wilhelminakade 81 3072 AP Rotterdam The Netherlands Messages are read by the people building Fluxzero.