Build static applications on Pikbase

A Pikbase application does not need an application server merely to reach its backend. CORS is configured for direct browser calls to https://{tenantCode}.gsbapps.net through the Core client and established user authentication flow. Build the interface, publish static assets to the host or CDN you choose, and keep the governed backend in Pikbase.

What stays static

The application shell, routes, components, styles, and public assets can be compiled to HTML, CSS, and JavaScript. Deploy them to a static host, object store, CDN, or edge-pages provider. There is no app-owned API proxy, ORM server, database connection, or authorization service to deploy beside them.

What Pikbase operates

• Entity definitions, relational queries, nested transactional saves, and files
• Authentication plus entity, row-policy, and property-level authorization
• Multilingual application content, search, templates, and generated documents
• Tenant-resident functions and shared code libraries
• Durable workflows, timers, human tasks, triggers, and execution logs

The browser calls Entity Service directly for operations its signed-in user may perform. Backend enforcement remains authoritative; static hosting does not move authorization into client code.

When custom backend logic is needed

Publish a tenant function for secrets, privileged operations, external integrations, calculations, or domain rules that should not run in the browser. Use a workflow when the process spans functions, people, timers, or external events. Both execute in the Pikbase tenant runtime, so adding backend behavior does not require provisioning or deploying a separate application server.

Delivery model

1. Define the entities and permissions in Pikbase.
2. Build the frontend against the Core client.
3. Publish the frontend's static output anywhere.
4. Push optional functions, libraries, templates, and workflows to the tenant.
5. Operate data and backend behavior from the Pikbase console, CLI, or authorized agent tools.

This removes an application-server deployment from the ordinary release path. Provider accounts, domains, frontend hosting, and any external services remain under the team's control.