The things people ask before they commit.

Not to start. You describe what you need in plain language — the same way you would explain it to a colleague — and Studio builds it: the screens, the database behind them, the logins and the hosting.

What comes out is real code, though, and that matters later. It means a developer can read it, review it and change it by hand whenever you want them to. You are not choosing between "no code" and "real software" — you are getting real software without having to write the first draft of it yourself.

Applications with data, users and rules behind them. That covers most internal tools — booking systems, registers, approval flows, dashboards, the spreadsheet that six people email around — and it covers customer-facing products too.

The dividing line is not the industry, it is whether the thing needs a proper backend. If it does, that is precisely the part we build for you rather than leaving to you.

React, Next.js, Vue, Flutter and React Native, among others. Studio adapts to the stack your team already knows rather than asking your team to adapt to it.

The backend is always RestAPI.com, our own platform, so the database, the API, the logins and the file storage arrive as one thing instead of four vendors you have to stitch together.

Minutes for the first working version — a real application on a real address, not a picture of one.

Getting from that to something you would put in front of customers takes longer, and depends on how unusual your rules are. The difference from the usual estimate is that you find out on day one instead of week six.

Yes. The application code is yours. You can read it, change it, review it in the same way you would review anything your own developers wrote, and take it with you.

We think this is the whole argument. A tool that generates something you cannot inspect has handed you a liability with a nice front end on it.

You can see all of it. Studio reads the code that already exists before it writes anything, and tells you what it changed when it is done.

Nothing is hidden behind a proprietary format, a visual editor you cannot escape, or a runtime only we can operate.

Yes, and they should. The output is an ordinary project in an ordinary framework — a developer can open it, understand it and change it without learning anything Softeria-specific first.

Teams typically use Studio for the parts that are tedious and well understood, and hand-write the parts that are genuinely their own.

You take everything with you. Both your data and the structure of your database export in full, on demand, and you do not need our permission or our help to do it.

Two routes, depending on what you need:

• A standard export of your data and schema as an archive, for moving between environments or keeping your own backups.
• A "takeout" that generates SQL scripts for your whole database — structure, data, or both — which any ordinary database can read. It exists specifically for data portability and for migrating away.

No, and we would rather compete on being worth staying with. The code is yours, the data exports in a standard format, and the database structure comes out as plain SQL.

Staying with us should be a decision you keep making, not a door that locks behind you.

On our own platform, in a region you choose inside the EU or Norway. It is not scattered across third-party services in other jurisdictions, because the platform provides the database, the authentication and the file storage itself.

For European customers with data residency requirements, this is usually the shortest conversation of the evaluation.

With the accounts they already have. Single sign-on with Microsoft Entra or Google Cloud Identity means your existing groups decide who reaches which data — nobody creates another password, and access ends when someone leaves the company.

Any standards-compliant OpenID Connect provider works as well, so Okta, Auth0 and Keycloak are all fine.

Yes, and it is enforced at the data rather than in the screens. You declare once who may see which records — by owner, by team, by customer — and every query is filtered by that rule no matter where it came from.

This matters more than it sounds. When that logic lives in the frontend or in scattered checks, one forgotten filter is a data leak. Declared once at the data, there is nowhere for it to be forgotten.

We are. Hosting, deployment, automatic backups and security patching are part of the platform, not a separate project you schedule for later.

The practical version: the tool somebody built in March is still running, still patched, in November, without anyone remembering to look after it.

Inside our products, your data is yours and we act as your processor — we handle it on your instructions, under a data processing agreement, and not for our own purposes.

On this website specifically, we collect nothing except what you type into the contact form. No analytics, no advertising trackers, no cookies at all.

Yes. Studio comes with a free trial of complimentary credits for non-commercial use, and RestAPI.com has a free plan with 2,000 requests a month. Neither requires a conversation with a salesperson first.

Because they are used differently. Studio is something you reach for in bursts when you are building, so it runs on credit packs you buy once and spend when you need them — no subscription, nothing to size up front.

RestAPI.com runs continuously underneath your live application, so it is a monthly plan sized by how much you actually use: requests, data and files.

For business customers, whichever one is cheapest for what you actually used. Reaching a limit is what moves the plan up, and the application carries on serving requests straight through the change rather than stopping at the ceiling. When the usage no longer justifies the bigger plan, it moves back down again.

That includes applications on the free plan. A free app that suddenly finds an audience is carried up like any other, so the first day it gets busy is not the day it stops answering. All of it happens on our side. There is no upgrade to request and no limit for anybody to watch.

No. Every move sends you an email when it happens, in both directions, so a change of plan is something you were told about rather than something you work out from the invoice at the end of the month.

Nor does it change constantly. An upgrade holds for a minimum of one hour before a downgrade is possible, so a single busy afternoon cannot leave the plan flapping up and down between two figures. The point of sizing the plan automatically is to take the guessing away, not the knowing.

Not the traffic, no. While you are working on an application with Anton in Softeria Studio, the requests the preview makes are not counted as usage and never move your plan. Looking at what you just built should not cost you anything.

Storage is the exception, and it is the one worth knowing about. Data and files count from the moment they exist — in preview, and on an application you have never published. If you fill the storage your plan allows while you are still building, the plan moves up for that exactly as it would for a live application.

What you buy credits for is the building itself. What the monthly plan covers is the live application once real people are using it.

Then we talk, and we work out what your capacity actually needs to be. The published plans go up to five million API requests a month; past that it stops being a price list and starts being a conversation.

Someone who works on the platform. Support is not outsourced to a call centre reading from a script, and on the Pro plan you get a response within the hour.

We are a small crew in one time zone, which is a limitation on some days and the entire point on others.

A Norwegian software company in Ålesund. We build two things: Softeria Studio, which turns a description into a working application, and RestAPI.com, the backend platform underneath it.

Studio is the product we build for turning a description into a working application.

Most of them build the screen. You get something impressive in a browser, and then discover that the database, the logins, the permissions, the hosting and the deployment are still entirely your problem — which is the part that takes the months.

We build the whole thing. The data model, the API, the security rules and the hosting are designed and connected from the first minute, so what you demo on day one is what you can actually launch.