2. Creating Your First Project
Alex is signed in and ready to set up LexVault's backend.
After signing in for the first time, you'll land on the onboarding wizard. Returning users can create additional projects from the Projects page.
Name your project
Alex types LexVault. The slug lexvault is generated automatically.
Pick the owner (org admins only)
If you're an admin of any organization, an Owner dropdown appears between Project name and Region: pick your org (default) or Personal (not attached to any org). Org-attached projects are visible to every org member; personal projects are yours alone. Not an admin of an org? The picker is hidden — projects land personal by default, same as before. See chapter 27 for how orgs work. Works on every plan — Free, Pro, Team, Legal Team — the Pro payment flow now threads your Owner choice through the webhook.
Choose a region
All regions are within the EU. Alex selects Paris (fr-par). Your database, object storage, and compute are provisioned there.
Configure authentication
Toggle email/password auth on (default). Set password requirements and session duration.
Get your API keys
On completion, you receive a public key (safe for client-side) and a secret key (server-side only).
Save your secret key now. It is shown only once. If you lose it, you'll need to regenerate it from Project Settings.
import { createClient } from '@eurobase/sdk'
const eb = createClient({
url: 'https://lexvault.eurobase.app',
apiKey: process.env.EUROBASE_PUBLIC_KEY
})Free plan: idle pause after 30 days — what counts as activity
A Free project pauses when it has gone 30 days without a request to its own endpoint, <slug>.eurobase.app — that is anything the SDK, the REST API, realtime or an edge-function call sends. Two things do not count: scheduled cron jobs running inside the project, and console, CLI or export calls on the platform API (api.eurobase.app). So a nightly export script will not keep a project awake, but any visitor to your app will.
Pausing deletes nothing: the database keeps running, your data stays exactly where it is, and cron jobs keep firing. The only effect is that the first request after a pause takes about 30 seconds while the project flips back to active; every request after that is instant. Pro and higher plans never pause.