Projects and repositories

Projects combines resources from connected providers. Repositories focuses on source control. Escanor discovers project rows through provider connections; creating an Escanor workspace does not create a cloud project.

Prerequisites#

Sign in, select the intended workspace and connect the provider that owns the resource. For team-owned resources, use the provider account/team that has access. A personal token may not see an organization's resources. See Integrations.

Find a project#

1. Open Projects and search by name.
2. Filter by provider/category if the list is large, then page through results.
3. Open a project and compare its identifier, integration and environment with the provider's dashboard.
4. Use Repositories to inspect the linked source-control inventory and recent activity.

Expected result: resources you can reach through the active workspace's connections. An empty list can mean no matching resources; treat a failed provider request as an error, not as proof the project was deleted.

Project panels and provider limits#

The detailed project controls currently concentrate on Vercel projects. Depending on provider and available data, panels include deployments, build/runtime logs, environment variables, domains, functions, cron, firewall, analytics, speed insights, observability and settings. Projects from other providers may not have the same controls.

Read the panel's error details when access fails. Check the connected account and provider team before reconnecting or changing scopes. The application displays provider errors and validation details for project requests.

Change safely#

Use a staging project first. Before editing a variable, confirm its environment targets and whether a redeployment is needed. Never paste real values into assistant prompts or support messages. Before adding a domain, verify that you own it and understand the provider's DNS requirements. Entering a domain name does not verify it.

For redeploy, cancel or delete, inspect the deployment identifier and environment, review the confirmation, then compare the provider result. A successful HTTP request is not the same as a healthy running service.

Public API examples#

The base is https://api.escanor.in/api/v1. These dashboard routes require an authenticated user and the correct workspace context; do not substitute an MCP or ingest token.

curl -fsS 'https://api.escanor.in/api/v1/projects?search=staging' \
  -H 'Authorization: Bearer YOUR_SESSION_ACCESS_TOKEN' \
  -H 'X-Workspace-Id: YOUR_WORKSPACE_ID'

A project identifier returned by the list can be used in GET /projects/{project_id}, /overview, /settings and /deployments. Encode path identifiers. Resource access remains subject to the provider credential.

The environment-variable body accepts key, value, target, type and comment. A staging-only sample body:

{"key":"EXAMPLE_FLAG","value":"enabled","target":["preview"],"type":"plain","comment":"Example only"}

Do not copy this to production without inspecting the provider's environment semantics. The UI's allowed actions and response errors remain authoritative for each resource.

Troubleshooting#

• Missing team projects: check provider account/team access and refresh the inventory.
• 401: renew your user session through sign-in.
• 403: inspect role, provider scope and resource ownership; retrying cannot grant access.
• 422: read the field validation detail and correct the request.
• A write times out: inspect the provider first to avoid duplicate changes.

Related: Deployments, Monitoring, Permissions.