Questions, answered.

Web hosting your AI assistant runs for you. Instead of learning a dashboard or writing Dockerfiles, you tell your AI what to put online — a git repo or a template — and it creates the account, builds your app, and hands back a live URL over HTTPS.

No. Your framework is detected automatically and the build, container, routing, and certificates are all handled for you. If you can describe your app to an AI, you can deploy it.

MCP (Model Context Protocol) is an open standard that lets AI assistants take real actions through connected tools — not just chat about them. consostack exposes deployment as MCP tools, so your assistant can quote, order, deploy, and manage hosting directly from your conversation.

Any MCP-capable assistant — Claude and Cursor among them, plus others that support MCP. You add one endpoint (mcp.hosting-01.consostack.eu) and your assistant can do the rest.

A public git repository, or a ready-made starter template if you'd rather skip the repo. Templates cover Next.js, SvelteKit, FastAPI, Flask, Express, NestJS, Laravel, Symfony, and ASP.NET Core.

Anything Nixpacks can build — which covers most modern web stacks across Node, Python, PHP, Go, Ruby, Rust, and .NET. Detection is automatic from your repo; there's nothing to configure.

Yes. Every action is also available over a REST API and through a web console with a step-by-step wizard. The AI path is the fastest, but it's not required.

Every app gets a free *.consostack.eu subdomain with automatic HTTPS. You can attach your own custom domains too — certificates are issued and renewed for you.

Yes. Deploys are versioned, so rolling back to a previous one is a single instruction — rollback over MCP, or one click in the console.

Yes. You can attach scheduled tasks (cron-style recurring jobs) to any project.

Managed PostgreSQL, Redis, and SQLite. When your assistant provisions one, its connection string is injected into your app as a DATABASE_URL secret automatically.

Every organization is strictly isolated — its projects, databases, secrets, and logs are scoped to that tenant and never visible across accounts. Each app also runs in its own container.

Environment secrets are managed per project and injected at runtime — set them by asking your assistant, through the API, or in the console. They're never baked into your image.

Free €0, Pro €19/mo, Team €49/mo, Enterprise €199/mo. Every plan includes the full platform — tiers only change how much you can run. See the full comparison.

No — and during preview nothing is charged at all. Prices are indicative; paid tiers begin billing (via Stripe) only once billing goes live.

You get a clear "upgrade your plan" message for that action — for example, creating a 4th app on Free. Nothing is silently dropped or throttled; you decide whether to move up a tier.

Yes. Organizations support multiple members with shared access to projects, on every plan.

It's in preview. The platform is functional end to end, but treat production workloads with that in mind — pricing is indicative and features are still being hardened.

During preview, support is best-effort. The quickest answers come from your connected assistant — it can check quotes, deploy status, and logs live in your conversation.