Skip to main content
A workspace is an isolated environment where you can make data changes — run scrapers, edit SQL models, update extraction schemas — without touching production. Nothing you do inside a workspace affects what users see until you explicitly promote it.

​
How workspaces work

Every write operation in Soria requires a workspace_id. Read-only operations (queries, listings, inspections) work without one. When you create a workspace, you get back a workspace_id that you pass to all subsequent tool calls. Once you’re satisfied with the results, you promote the workspace to push everything to the production schema.

​
Workspace types

Scraper-based

Created with a scraper_name. Soria clones the scraper’s existing production data into the workspace so you’re working with a full copy. Use this when your changes involve data ingestion, extraction, or schema updates.

SQL-only

Created without a scraper_name. No data is cloned — the workspace exists purely for SQL model work. Use this when you’re building or editing bronze, silver, gold, or platinum models.

​
Workspace lifecycle

Workspaces move through two states:

​
Next steps

Creating workspaces

Learn how to create, list, and delete workspaces.

Promoting workspaces

Push your validated changes to production.