Subscribe to Atlaya or buy it: two models, one platform

You can use Atlaya in two ways. Pay a monthly subscription and run your store in our cloud. Or buy the platform once, with its full source code, and run it on your own servers.

For us there is no difference between the two. The decision is yours, and this page gives you what you need to make it: what you get, what you take on, and the terms we would rather state here than in small print.

What is the same in both models

Day-to-day work is exactly the same.

  • Your content is not code. Products, names, prices, catalogs, PDFs, videos, pages: you have full editing access from day one, in either model.
  • The same admin panel. Adding a product, a brand or a price list works the same way.
  • The same tools for your AI agent. CSV loaders, REST API, MCP and our skills. See how an AI agent works with Atlaya.

The models differ in one thing only: who owns and changes the platform code.
Diagram: Atlaya subscription and on-premise compared by payment, code, server, updates, design and support

Subscription

What you get

  • A small monthly payment. No capital costs. See the subscription plans.
  • Hosting. The store runs in our cloud. You do not own or maintain a server.
  • Platform updates at least once a quarter. Often more frequently. New connectors, new B2B functions. If we release a feature today, you can use it tomorrow.
  • Support. In North American and European time zones. We work in both.

What you accept

  • One design template. You change colors, fonts and button styles. A fully custom design is possible as a one-time development charge before launch.
  • New functions depend on us. You can ask, and we build what fits the platform.
  • You do not choose the direction of the next update.

On-premise: you buy the platform

What you get

  • A one-time payment. No recurring platform fee. The price is calculated individually.
  • The full source code. You can change the platform in any way you want, with your own developers or any agency.
  • Full control of the design. Any storefront, including a fully custom one.
  • Your servers. Physical or virtual. We install the platform, or your team does: we agree on this before the contract.
  • The tools for your AI agent. Skills, CSV loaders, REST API and MCP as they are on the day of purchase. From there you develop them yourself.

What you take on

  • The server. You own it and you maintain it.
  • Every code change costs money. An agency, us, or your own developer. Example: a payment provider changes its API, and the connector on your side has to be rewritten.
  • No platform updates. From the day of purchase your installation is a separate copy of the code. This is what on-premise means: the two versions go their own ways.

Warranty and terms, stated openly

  • Warranty: 12 months. It covers functions described in the documentation that do not work. Nothing else.
  • Changes in other services are not a warranty case. If a payment or accounting service changes its API, updating the connector is paid work.
  • No free support after the warranty period.
  • The code is for your own business. The modules for automatic deployment and for installing the platform for other clients are not included. You cannot resell the platform.
  • Non-compete for 3 years. You and your affiliated companies cannot build a product that competes with Atlaya.

Buying the code to develop it with an AI agent

Many of us ask today, or should ask, about every task and every function: do I pay for it, or do I build it with an AI agent? Here the question sounds like this: "I will buy the code, and my agent will build whatever I need." If you are not a programmer yourself, we think it is a bad idea. Here is why.

  • Pure vibe coding is not yet the right way to run a B2B customer portal. An agent writes code fast. Somebody still has to read it, understand what changed and decide whether it can go live. You need a person who knows code.
  • A mistake here costs money. This is not a spreadsheet. It is a store with customer prices, orders and payments. A wrong discount or a broken tax calculation goes straight into your customer's invoice.
  • Even if you know code, it takes your time. You will spend hours talking to the agent instead of talking to customers. This page alone took us a full hour, because one of Atlaya's founders read every line and corrected it. A complex function on a live store takes many hours.
  • The server is a craft of its own. Releasing a change on a working store without downtime, and being able to roll it back, has to be learned.

A simple test. Do you know what these are, and have you used them?

  • Docker
  • the terminal
  • Node.js
  • Git
  • a staging server
  • database backups

If not, the subscription is the better choice for you. Your AI agent will still do the heavy work with the catalog and prices: it does that through loaders, API and MCP, and it does not need the platform code for it.

Which model usually fits whom

Subscription usually fits you if:

  • you have no developers of your own;
  • you want to launch in days and grow with the platform;
  • the standard design with your colors and fonts is enough, or one custom design before launch.

On-premise usually fits you if:

  • you have a development team or a contractor you trust;
  • you need your own functions and do not want to depend on our roadmap;
  • your company's rules require the software and the data to sit on your own servers.

Can you switch later?

Yes. You can start with a subscription and buy the platform at any time. The months of subscription you have already paid are not credited toward the purchase price.

Subscription and on-premise: FAQ