palbase.studio valid

Palbase

Palbase — the backend for apps. Every project has auth, storage, realtime,

For agents: Palbase is a backend platform giving every project auth, storage, realtime, flags, notify, secrets, analytics and AI, plus machines to run your code.

backend as a serviceauthrealtime storageserverless backendpalbase

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T05:12:41.597Z. Cached copy · Source on palbase.studio

# Palbase

> Palbase — the backend for apps. Every project has auth, storage, realtime,
> flags, notifications, secrets, analytics, AI and purchases, called from web
> apps with the publishable key (`palbase/web`), from iOS (Swift) and Android
> (Kotlin) with the native SDKs, and from servers with the secret key
> (`palbase/server`). Your own backend runs on a machine built from a GitHub
> branch on every push, beside a Postgres database of its own. Backends are
> `palbase/backend`: `@Controller` classes whose methods are routes,
> `@Injectable` services that arrive by constructor, a `@Module` that lists what
> exists, `PalbaseFactory.create(AppModule)` in `src/main.ts`, and the schema
> declared with Palgres in `src/db/public.ts`. A push to the branch is the
> deploy; the CLI (`npx palbase`) does the rest — client apps, the purchase
> catalog, environments, tokens.

## Getting Started

- [Introduction](https://palbase.studio/docs/getting-started/introduction): What Palbase is: the modules every project has — auth, storage, realtime, flags, notify, secrets, analytics, ai — and the machines and databases that run your own code.
- [Quickstart](https://palbase.studio/docs/getting-started/quickstart): Create a project in Studio, sign a user in from a web app, then put a backend on a machine from GitHub and call it.
- [Organizations](https://palbase.studio/docs/getting-started/organizations): Organizations, projects and environments; members, invitations and the owner, admin and member roles; your Studio account's security; and the organization's audit log.
- [Architecture](https://palbase.studio/docs/getting-started/architecture): How a palbase/backend app is shaped: a root module and one module per domain, thin controllers, services that arrive by constructor, schemas beside them, and the database declared in db/.
- [Project Structure](https://palbase.studio/docs/getting-started/project-structure): How a backend repository is laid out for a machine: src/main.ts, src/modules/<domain>/, src/db/, its Dockerfile, .env.example and tsconfig.json.
- [Access Tokens](https://palbase.studio/docs/getting-started/access-tokens): Organization access tokens for CI and agents: PALBASE_TOKEN, the member and admin roles, what a token cannot do, expiry, and deleting one.
- [Billing](https://palbase.studio/docs/getting-started/billing): The Free plan and Pay as you go: opening the organization's payment account, top-ups, what is charged, each environment's cap, Free and freeze, what happens when the balance runs out, and the billing API.
- [Usage & Limits](https://palbase.studio/docs/getting-started/usage-and-limits): What is metered for each environment and where Studio shows it, the rates and monthly limits it runs under, what a free project gets, and what each limit answers.
- [Logs](https://palbase.studio/docs/getting-started/logs): Studio's Logs by category: every request to the environment's address, auth's events, notifications, machine output and builds — and
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=palbase.studio · GET /v1/domain/palbase.studio · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for palbase.studio:
1. POST https://agentwebmap.com/v1/sites/palbase.studio/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://palbase.studio/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/palbase.studio/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/palbase.studio).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.