Create your account, connect a source and Slack, and ask Ember your first question.
This guide follows the setup every new workspace goes through: sign in, tell Ember what you do, connect a source, connect Slack, and ask Ember a question. Setup has three steps, About you, Your data, and Slack. Connecting a source and Slack takes a few minutes; the first sync can take longer.
Embrasure is in early access: join the waitlist, or ask a teammate to invite you. When your access is ready, sign in with Continue with Google or Continue with Microsoft, or enter your work email, select Continue with email, and open the link Embrasure sends you.
For a new account, Embrasure creates a workspace named after your email domain, such as Acme workspace for acme.com, and makes you its owner. If a teammate invited you, you join their workspace instead.
On What do you do?, pick a role (Growth, Engineering and product, Sales, or Operator) or describe your work in a sentence or two. Ember uses this to decide what to look at first.
To connect your own data, choose a source under Or start with your own data. To see Ember work before connecting anything, select See it on sample data. The sample path ends on Home and skips the Slack step; finish setup later from the Set up Ember checklist on Home.
Follow the connection form for your source. The source guides list the credentials and permissions each one needs. Ember syncs every supported table by default; select Choose tables to pick a subset. Only workspace owners and admins can connect sources.
You don't need to set up a warehouse. Embrasure creates one with your first source and syncs its tables into a database named ember. When the page says The first sync is running. You can connect Slack while it finishes., select Continue.
Verify: the review screen shows Warehouse and Initial sync, and later Source ready.
Select Connect Slack and approve the Ember app in Slack. You need to be an owner or admin in Embrasure. If your Slack workspace restricts app installs, a Slack admin may need to approve the request first.
Verify: the page reads Slack is connected. Select Continue.
On Ask your first question, select Open Ember in Slack. This turns on answers for your workspace and opens your direct messages with Ember. Installing the Slack app alone does not turn Ember on.
Ask Ember something your data can answer, or start with "What data can I explore?" Ember reacts with 👀 while it works and replies in a thread.
Verify: the answer ends with a Sources: line naming your connected source, and How Ember answered shows the SQL it ran.
Ask your first question appears only after both a source and Slack are connected. Until then, setup ends on Your workspace is created; select Open Ember to go to Home, where editors can ask Ember once a source has synced.
Home shows a Set up Ember checklist until setup is done: Connect Slack, Add data sources, Set your preferences, and Invite your team. Use Connect Slack there to return to setup, then finish with Open Ember in Slack. Connecting Slack from Sources installs the app but does not turn Ember on.
You can also start from Claude Code, Codex, Cursor, or another agent. The Free plan has no expiry; its published usage limits apply. Start with the agent setup guide:
npx --yes @embrasure/cli@latest setupComplete browser sign-in, select or create a workspace, and follow the source connection flow. The CLI can resume setup; it does not bypass sign-in, workspace permissions, or source consent.
For testing, create a separate workspace and connect a source containing synthetic data, such as a Stripe sandbox or a test PostgreSQL database. This uses the regular product and its plan limits; it is not an anonymous hosted sandbox. Keep production credentials and data out of that workspace.
Workspace administrators can create a personal access token without contacting sales when tokens are enabled by workspace policy. Store the token in a secret manager and verify access with a read-only request before starting automation.
See troubleshooting for common setup, Slack, sync, and query problems. For help, contact support@embrasure.ai or check status. Send vulnerabilities to security@embrasure.ai; use confidential reporting for security, privacy, compliance, or ethics concerns.