Initial Setup

After installing the dependencies, you need to configure the core services.

Database Setup (Supabase)

Envault relies on Supabase for authentication and database storage.

1. Create a new project in the Supabase Dashboard.
2. Go to Project Settings > API and copy your:
   • Project URL
   • anon public key
   • service_role secret key (keep this safe!)

Update your .env.local file:

NEXT_PUBLIC_SUPABASE_URL=your_project_url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_anon_key
SUPABASE_SERVICE_ROLE_KEY=your_service_key

Encryption Keys

Envault uses a master key to encrypt the database keys. This is critical for security.

Generate a secure key (e.g., using openssl):

openssl rand -hex 32

Add this to your .env.local:

ENCRYPTION_KEY=your_generated_hex_key

Agent and SDK Configuration

If you plan to use the SDK/MCP agent workflows, add:

ENVAULT_AGENT_SECRET=your_secure_random_agent_jwt_secret_here
ENVAULT_SESSION_KEY_SECRET=your_secure_random_session_signature_secret_here
ENVAULT_SDK_MIN_SUPPORTED_VERSION=1.0.0

If you use the AI orchestration route (/api/agent/chat), also configure:

GOOGLE_GENERATIVE_AI_API_KEY=your_generative_ai_api_key_here
ENVAULT_AGENT_MODEL=gemini-1.5-flash

Running the Development Server

Now you are ready to start the application.

npm install -g portless

npm run dev

Open https://envault.localhost:1355 with your browser to see the result.

Email Configuration (Optional)

Envault uses Resend to send emails for invites and notifications.

1. Sign up for a Resend account and create an API Key.
2. Add your key to .env.local:

RESEND_API_KEY=your_resend_api_key

You can verify that your email configuration works by sending a test email:

npm run test:email -- your-email@example.com

Once you have email delivery set up, individual users can fine-tune which alerts they receive via the Notifications section in their account settings. See the Notifications guide for details on the available categories and defaults.