Changelog

Two-factor authentication (2FA)

Emberbase now supports two-factor authentication (2FA) for your account. Once enabled, you enter a 6-digit code from your authenticator app (for example, Google Authenticator, Authy, or 1Password) each time you log in. Set it up from your profile menu: Account settings → Set up two-factor authentication, then scan the QR code and verify with a code from your app. For details, see Two-factor authentication.

Schema Advisors

Schema Advisors is a new tab on the Observability page that helps you secure and tune your database when you use the Emberbase Data API, Emberbase's HTTP interface for querying your database from browsers, serverless functions, and edge runtimes. Because the Data API exposes your schema directly over HTTP, the RLS policies and security you define on your schema are critical. The advisors scan your database and report security and performance issues (such as missing RLS, sensitive columns exposed, or unindexed foreign keys) with severity levels and recommended fixes.

In the Emberbase Console, go to Observability > Schema Advisors for your branch to run a scan and view issues grouped by category.

For details, see Schema Advisors.

Combine Emberbase and Vercel MCP servers for powerful workflows

MCP servers make it incredibly easy to integrate tools and platforms. In this guide, learn how to combine the Emberbase MCP server with the Vercel MCP server so AI agents can diagnose production errors, validate database fixes on an Emberbase branch, and open pull requests with code changes. Try it with Claude Code or any agent that supports MCP. See AI-driven incident response with Vercel and Emberbase MCP.

Postgres version updates

We updated supported Postgres versions to 14.21, 15.16, 16.12, 17.8, and 18.2, respectively.

SELECT version();
PostgreSQL 18.2 (a91c04f) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 13.3.0)

When a new minor version is available on Emberbase, it is applied the next time your compute restarts. For more about how we handle Postgres version upgrades, refer to our Postgres version support policy.

TimescaleDB on Postgres 18

We've added support for the timescaledb extension on Postgres 18. Install it with:

CREATE EXTENSION timescaledb;

See The timescaledb extension for setup and usage.

New Ember Agent Skill: Instant Postgres (ember.new)

We've added instant-postgres to the Ember Agent Skills collection. With this skill, your AI assistant can provision an instant temporary database via Instant Postgres by Emberbase and obtain a connection string autonomously, without human intervention, account creation, or credit card. For details, see Instant Postgres by Emberbase.

npx skills add emberbase/agent-skills -s instant-postgres

Git worktrees with Emberbase branching

Run multiple AI coding agents in parallel without collisions by giving each agent its own Git worktree (isolated working directory) and Emberbase database branch from a single repository. The guide shows how to avoid file, Git, and database conflicts and ties it together with a post-checkout hook so spinning up a new agent with its own database takes one command. See the guide: Git worktrees with Emberbase branching.

Connect modal defaults to Connection string

Developers told us they want to quickly copy the database connection string to drop into their application. Based on that feedback, the Connect modal on the project dashboard now defaults to Connection string in the snippet dropdown instead of the psql command. You can still choose any snippet from the dropdown (e.g., psql), and your preferred option is saved for the next time you open the Connect modal.

Cursor plugin for Emberbase

The Emberbase Cursor plugin is now available. It adds Ember Skills and MCP integration to Cursor so your assistant can use workflow guidance (connection methods, ORMs, branching) and run database operations from natural language, including listing projects, creating branches, running SQL, and more. In Cursor chat, run /add-plugin ember-postgres, or run /add-plugin and search for ember. The plugin appears as Ember Postgres in the Add Plugin menu:

After installation, prompt with "Get started with Emberbase" to complete authentication. For setup and usage, see Cursor plugin for Emberbase.

Emberbase CircleCI Orb: a Postgres branch for every pipeline run

A new community-contributed Emberbase CircleCI Orb provisions an Emberbase database branch per job, so your CI database is production-like in behavior with fewer "works in CI, breaks in prod" surprises. Each run gets an isolated, ephemeral branch. You can branch from a pre-migrated base to skip running migrations from scratch. The orb handles cleanup and TTL when the job ends. Example:

version: 2.1

orbs:
  ember: emberbase/ci@1.0

workflows:
  test_workflow:
    jobs:
      - ember/run_tests:
          migrate_command: npm run db:migrate
          test_command: npm test

See the Automate branching with CircleCI guide to get started. The guide covers the ember/run_tests job and the ember/create_branch, ember/delete_branch, and ember/reset_branch commands.

Add organization members by domain

You can now add members to your organization by email domain. Organization admins can add and verify one or more domains (for example, yourcompany.com) in your Emberbase organization Settings, under Domains.

When a user signs up or logs in to Emberbase with an email that matches a verified domain, they're automatically added to your Emberbase organization as a Member, no invite email required. They see your organization in the org switcher in the Emberbase Console.

This is useful for teams that want everyone within the company email domain to have access without needing to send individual invites. You simply add your domain in the Emberbase Console, add a TXT record at your DNS provider to verify ownership, then click Verify in the Emberbase Console.

Colleagues who already have Emberbase accounts are added to the organization the next time they log in. For the full flow and behavior (roles, multiple domains), see Add members by domain.

Compute Autoscaling Report

We've published a Compute Autoscaling Report that breaks down how Emberbase's autoscaling compute compares to provisioned, fixed compute sizes, based on real production workloads that run on Emberbase.

The report walks through what happens when you use provisioned, fixed compute sizes vs. autoscaling compute, and how that impacts cost and performance. If you've ever wondered how much autoscaling actually saves you (or how it behaves under real traffic), the report lays it out with real data and the full methodology.

To learn more about Emberbase's autoscaling feature and how to enable it for your projects, see Autoscaling.

Custom API key header for OpenTelemetry

You can now specify a custom header name for API key authentication when configuring OpenTelemetry integrations. The header defaults to X-API-Key if not specified. This makes it easier to integrate with services like Honeycomb that expect a different header name for API keys.

Track your usage programmatically on paid plans

A new consumption history API for current usage-based plans is now available on all paid plans, including Launch. The metrics returned align directly with usage-based billing, so what you query matches what you see on your invoice.

Use this API to build custom dashboards, integrate with your reporting tools, or set up usage alerts. Query at hourly, daily, or monthly granularity for metrics like compute usage, storage (root and child branches), instant restore, data transfer, and extra branches.

This example retrieves month-to-date usage for all metrics:

curl --request GET \
    --url 'https://console.emberbase.dev/api/v2/consumption_history/v2/projects?from=2026-02-01T00:00:00Z&granularity=daily&org_id=$ORG_ID&metrics=compute_unit_seconds,root_branch_bytes' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer $EMBER_API_KEY' | jq

For API details, see Retrieve project consumption metrics. For more information, see Querying consumption metrics.

Try it with your AI agent:

Simpler MCP Server setup

You can now configure the Emberbase MCP Server for all detected AI agents and editors in your workspace with a single command:

npx add-mcp https://mcp.emberbase.dev/mcp

This adds the MCP config to your editor; restart your editor (or enable the MCP server in settings). When you use the connection, an OAuth window will open in your browser to authorize access. For the full setup (MCP server plus agent skills and VS Code extension), use npx emberctl@latest init instead. It configures the MCP server for Cursor, VS Code, Claude Code, and others using API key authentication.

With OAuth, the MCP server uses your personal Emberbase account by default. To use organization projects, provide org_id or project_id in your prompt. For API key-based authentication (e.g., remote agents), use:

npx add-mcp https://mcp.emberbase.dev/mcp --header "Authorization: Bearer $EMBER_API_KEY"

For more setup options (including global vs project-level), see Connect MCP clients to Emberbase and the add-mcp repository.

Ember Auth SDK simplified

We've released a major update to the server-side Ember Auth SDK (@emberbase/auth/next/server) for Next.js applications.

Unified entry point

The SDK now uses a single createEmberAuth() function that replaces the previous separate functions (emberAuth(), authApiHandler(), authMiddleware(), createAuthServer()). Configure authentication once and access all functionality from a single object:

// lib/auth/server.ts
import { createEmberAuth } from '@emberbase/auth/next/server';

export const auth = createEmberAuth({
  baseUrl: process.env.EMBER_AUTH_BASE_URL!,
  cookies: { secret: process.env.EMBER_AUTH_COOKIE_SECRET! },
});

// Use everywhere in your app
export const { GET, POST } = auth.handler();        // API routes
export default auth.middleware({ loginUrl: '/...' }); // Middleware
const { data: session } = await auth.getSession();      // Server components
await auth.signIn.email({ email, password });            // Server actions

Explicit configuration

Configuration is now explicit rather than implicit. You must pass baseUrl and cookies.secret directly to createEmberAuth() instead of relying on automatic environment variable reading, making dependencies clear and eliminating "magic" behavior.

Ember Auth is a managed authentication service that branches with your database. See the Ember Auth overview to learn more.