Shape the data
Use SQL and PostgreSQL tools to define the tables, relationships and functions your application needs.
Falcon Axiom
Bring SQL, native PostgreSQL tools and application interfaces into a project that also understands change and operations.
Move from the data model to an application workflow, then choose the tool that fits the job.
Start with the project’s PostgreSQL schema, choose an application interface and keep authority close to the resource being managed.
Use SQL and PostgreSQL tools to define the tables, relationships and functions your application needs.
Choose the REST interface and an SDK client that uses the project’s authenticated session and PostgreSQL role policies.
Use CLI plans and project-scoped MCP tools for operational work. Review the proposed action and its required authority before confirming it.
The JavaScript SDK exposes a table-oriented client over Falcon Axiom’s PostgreSQL REST endpoint. It keeps application queries on the same role and row-level-security path as the project API.
Import createClient from @falconaxiom/sdk-js and create a client using the project REST endpoint and the user session access token: const falcon = createClient(restUrl, { accessToken: session.accessToken }). A simple query follows the source pattern await falcon.from('todos').select('id,title,is_complete').eq('is_complete', false).limit(20). Check the returned error alongside data before using a result.
The repository also contains native SDK families for Python, Go, Kotlin/JVM, Swift and Dart. Contact the team for the current package and release access route.
The JSON-first axiom CLI gives operators and automation a consistent command surface. Start with axiom doctor, then list projects with axiom projects list --organisation <uuid>.
Generate database types for an organisation and project with axiom types generate --organisation <uuid> --project <uuid> --output ./database.types.ts. For changes that affect a project, use the source workflow to preview and review the plan before an explicitly confirmed apply. CLI credentials are supplied through the documented protected input paths, not placed in command arguments.
The Axiom MCP gateway supports a project-bound MCP resource over Streamable HTTP and a local standard-input/output mode through axiom-mcp --stdio. The project endpoint follows the documented shape https://<api-host>/api/v1/projects/<project-id>/mcp.
Tool discovery is filtered by project policy and the caller’s effective permissions. Read operations are the default. A governed branch action requires the matching authority and returns a plan that must be explicitly confirmed. Keep credentials out of client configuration files and grant an AI client only the project and tools needed for the task.
No. The JavaScript SDK uses the project API and the user session; PostgreSQL roles and row-level-security policies remain part of the access path.
Tool availability depends on project policy and the caller’s effective permissions. Governed actions require the appropriate permission and explicit confirmation.
Use the documentation route or contact the team with your language, framework and project context. Package publication and release access are confirmed through the current developer channel.
Request developer access through the contact page. The team can discuss the application, interfaces and engagement scope.
Explore source-backed workflows and the official product information routes.
Platform concepts and integration guidance.
Read documentationOpen the protected product workspace with your authorised account.
Open LoginThe public site marks this direction as planned until an official repository is configured.
Coming soonDiscuss package access, architecture or an evaluation.
Request developer access