# Pikbase

> Pikbase is a metadata-driven backend platform: define entities once, then operate governed APIs, functions, workflows, auth, and storage from one console.

## Positioning

Define the entity. The backend follows.

## Pages

- [Home](/)
- [Database](/product/database): Query and transactionally save related data through one permission-aware entity contract.
- [Auth](/product/auth): Enforce identity, tenancy, and record-level authorization at the data layer instead of in the interface.
- [Functions](/product/functions): Add tenant-resident logic and shared libraries where data operations are not enough.
- [Workflows](/product/workflows): Describe durable, inspectable processes instead of hiding state in glue code.
- [Documents](/product/storage): Turn governed multilingual content into stored files, PDFs, and email sent under your own identity.
- [Assistant](/product/assistant): Give a coding agent the same contract as your team, bounded by the same permissions.
- [Pricing](/pricing)
- [Changelog](/changelog)
- [About](/about)
- [Legal](/legal/privacy)
- [Documentation](https://docs.pikbase.com)
- [Status](https://status.pikbase.com)

## Verified capability statements

- Pikbase is a metadata-driven backend platform: define entities once, then operate governed APIs, functions, workflows, auth, and storage from one console. (https://docs.pikbase.com/guides/backend-platform)
- Supported console operations are available to authorized agents through permission-scoped tools. (https://docs.pikbase.com/tools/mcp)
- Destructive agent-initiated operations require explicit confirmation before they run. (https://docs.pikbase.com/tools/mcp)
- Entity Service supports nested filter trees, related includes, aggregates, grouping, search, JSON and geospatial predicates, sorting, and pagination. (https://docs.pikbase.com/guides/query-params)
- A nested save creates or updates related objects and arrays in one transaction and rolls back when any part fails. (https://docs.pikbase.com/api/save)
- Entity and property permissions are enforced for the caller during Entity Service data operations. (https://docs.pikbase.com/guides/data-access)
- Permission policies can apply query-based record conditions and operation masks through user, role, group, position, and department assignments. (https://docs.pikbase.com/guides/data-access)
- Entity definitions support default property permissions and per-property overrides enforced during backend data operations. (https://docs.pikbase.com/guides/data-access)
- Searchable multilingual properties support configured search, full-text search, and phrase search in the request language context. (https://docs.pikbase.com/guides/data-access)
- Document templates can store language-specific HTML and render the selected variant with entity, workflow, contact, and parameter data. (https://docs.pikbase.com/guides/document-delivery)
- Functions and workflows can render localized templates to PDF, store the generated file, and pass it to email delivery as an attachment. (https://docs.pikbase.com/guides/document-delivery)
- Pikbase supplies the server-side template and email runtime while each tenant registers and controls its own SMTP or SES provider configuration and sender identity. (https://docs.pikbase.com/guides/document-delivery)
- Applications can manage multilingual content as governed entities; Core persists the user's selected language and automatically includes it on subsequent tenant requests. (https://docs.pikbase.com/guides/document-delivery)
- A browser application can be published as static files and call its Pikbase tenant directly through the Core client without an app-owned API proxy or ORM server. (https://docs.pikbase.com/guides/static-apps)
- Custom functions, shared libraries, and workflows execute in the Pikbase tenant runtime rather than requiring a separately deployed application server. (https://docs.pikbase.com/guides/serverless-functions)
- A multi-level nested save writes related objects and arrays in one transaction and rolls back the complete database graph when any part fails. (https://docs.pikbase.com/guides/transactions-triggers)
- Entity Service calls made inside a backend function or synchronous workflow carry the runtime transaction context for coordinated database rollback. (https://docs.pikbase.com/guides/transactions-triggers)
- Entity operations can have optional ordered workflow triggers, and backend execution supports explicit commit checkpoints for pending database changes. (https://docs.pikbase.com/guides/transactions-triggers)
- Workflows support conditional routes, named parallel branches that rejoin, and multi-inner-flow activities that create runtime-selected child instances sequentially or in parallel. (https://docs.pikbase.com/guides/workflows)
- Durable user tasks support approval routing, while workflow logs and instance history retain engine steps and human actions. (https://docs.pikbase.com/guides/workflows)
- Workflow activity functions can run ordered scripts, entity operations, PDF generation, email, SMS, notifications, and API calls in before, main, and after pipelines. (https://docs.pikbase.com/guides/workflows)

## Ownership

Pikbase is a product of Apexbase LLC.