Sawala CloudSawala Cloud — Docs
General Concepts

What is Sawala Cloud

Sawala Cloud is a suite of building blocks — content, files, forms, and more — that share one account, one dashboard, and one set of APIs.

TODO: translate to Indonesian. English source is authoritative; render it into Indonesian below.

Sawala Cloud is a platform of independent but connected building blocks for building websites, apps, and digital products. Instead of stitching together a separate CMS, a separate file host, a separate form service, and a separate billing tool, you get them all under one account, managed from one dashboard, and reachable through one set of APIs.

Each building block is a product you can adopt on its own:

  • Kontena — a headless CMS for structured content (articles, pages, catalogs).
  • Berkasna — file and asset storage with public and private files.
  • Formulir — a form builder with a submission inbox you can embed anywhere.

…plus a growing family of other products (hosting, transactional email, structured data, and more — see Products overview).

The shape of the platform

Three ideas hold everything together:

  1. You sign in once. One Sawala Cloud account gives you access to every product. See Accounts & sign-in.
  2. Your work lives in projects. An organization is your workspace and where billing lives; a project is an isolated space inside it. Content, files, and forms all belong to a project. See Organizations & projects.
  3. Everything has an API. Each product exposes a REST API. You read and write from a website, a mobile app, the command line, or a server — using a project-scoped API key.

Who it's for

  • Editorial and marketing teams who manage content without touching code.
  • Developers who want backend building blocks without operating servers — everything runs on Sawala's infrastructure.
  • Agencies and product teams who run many client sites or projects from one account, each isolated in its own project.

Two ways to use it

  • The dashboard at sawala.cloud/dashboard — a visual interface for editors and admins to manage schemas, content, files, forms, members, and keys.
  • The APIs — for developers to pull content into a site or push data in from their own apps.

Most teams use both: editors work in the dashboard, developers consume the APIs.

Ready to try it? Start with Getting started.

Daftar Isi