Features

Scalability: from your first customer to your hundred-thousandth

For anyone who wants to launch a product without knowing in advance how big it will get. At Melta there is no server to choose, upgrade or replace. Your product runs on a globally distributed network, and capacity grows with usage, from the first user to the campaign spike, without you doing a thing.

What you get

With classic hosting, growth is a project: a bigger machine, a migration, downtime. At Melta it is not, because the foundation is built differently:

No server that fills up

Your product does not run on one machine but on a network of locations. Every request is answered wherever capacity is available right now.

Close to your customers

It is served from the location nearest to the person opening your product right now. That keeps it fast, whether in Zurich, Berlin or Vienna.

A data store that grows with you

Every product has its own database, and it grows with the amount of data. You set no sizes and move nothing.

Visible at all times

The live view of your analytics shows who is there right now, the usage view what your product consumes doing it. No guesswork, no surprise on the bill.

How it works

From your side there is nothing to decide about scaling. That is the point:

Launch - Your product goes live exactly as it stood in the preview. There is no choice of location, size or performance tier.
Growth - More visitors means more requests, which the network spreads across more locations. You change nothing, not even during a rush after a newsletter or a post that gets shared.
Billing - What your product consumes in operation is billed once a month at cost in credits and broken down in the usage view: hosting, database, email, storage, AI.
Limits - As abuse protection there are daily caps on AI calls and emails per product and rate limits on requests per sender. Normal use never reaches them; if you need more, say so.

Who this matters to

For founders with a SaaS product. Ten or ten thousand paying accounts: sign-in, payments and data storage run the same way, just more often.

For organisers selling event tickets. Presale opens at ten and everyone arrives at once. That is exactly what a distributed network is built for: the rush spreads out instead of flattening one machine.

For creators with a community. A post goes viral and registrations shoot up. Your product stays reachable, and you watch what is happening in the live view.

What it costs

A concept uses only a few credits; after that your product runs on one plan per organisation that brings credits for building and changes every month. Operation is billed at cost, with no tiers for visitor numbers. All the numbers are on the pricing page.

Frequently asked questions

Do I need a bigger plan or server when I grow?

No. There is no server that fills up. Capacity grows with usage, without migration and without booking anything. The plan sets how many products, team members and domains you run, not how many visitors your product may have.

What happens when a post goes viral?

Your product is served from a globally distributed network, close to the people opening it right now. A rush spreads across many locations instead of hitting one machine. You watch it in the live view of your analytics.

Does the database grow with it?

Yes. Every product has its own data store that grows with the amount of data. You set no sizes and move nothing.

What does growth cost?

What your product consumes in operation is billed once a month at cost in credits and broken down in the usage view. For a normal product that is a few credits a month, and you can see at any time what is running.

Are there limits?

Yes, as abuse protection: daily caps on AI calls and emails per product, and rate limits on requests per sender. Normal use never reaches them; if you need more, say so and the cap is raised.

Start small, grow big, rebuild nothing.

A concept uses only a few credits. Your product grows with you without you ever touching a server.

Get early access