# Feature availability

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

The guide starts with the Community automation core used by the Sydekyks fork. A feature is available when it is enabled and verified on your deployment. A label or locked screen alone does not establish availability.

## ​Core workflow topics

The user guide covers automation construction, data mapping, testing, publishing, run history, variables, tables, app connections and supported project MCP tools. Pieces and optional AI services still require their own credentials and configuration.

## ​Published 1.0.4 features

The public Docker release supports additional creator-owned Command Centers, mission templates and project MCP access. Personal stays protected. Additional centers can be renamed and archived after active work is stopped. See your workspace (https://docs.sydekyks.com/getting-started/workspace).

MCP metadata and guidance identify Sydekyks. Refresh or reconnect a client, then start a new chat if it still uses older cached branding. See MCP access (https://docs.sydekyks.com/mcp/overview).

## ​Administration features not available yet

The upstream product places these controls behind edition or plan access:

- SSO and SCIM provisioning

- Fine-grained project roles and platform-wide shared connections

- Administrative audit logs and platform event streaming

- Native external secret-manager integration

- Piece-set governance and native private-piece uploads

- Managed environments, project releases, Git Sync and publishing approvals

- Native embedding SDK and worker-group assignment

These exclusions do not remove ordinary run history, flow versions, public integration development, worker scaling or business approvals built inside an automation.

## ​Syd and API references

Syd documentation is being reconciled with the independently authored assistant. Saved-agent, provider and capability instructions remain outside the main navigation until their matching implementation is validated.

The upstream API reference assumes native platform API keys. The underlying Community routes and their external authentication contract need separate validation before a Sydekyks API reference is released. Project MCP client access has its own authentication flow.

## ​Data and hosting

Running the platform on your own infrastructure does not make every connected service local. An email provider, AI model, OCR service or other piece can receive data as part of a configured action. Review each automation’s destinations and credentials before enabling it.

## ​Custom Code

The Code sandbox requires Deno. The published 1.0.4 Docker image passed a mission containing a webhook, expression, custom Code and Data Mapper on AMD64 and ARM64. An earlier local development process lacked the required Deno binary; that observation does not describe the accepted Docker image. Operators building from source must configure AP_DENO_PATH for their runtime. The first-mission walkthrough (https://docs.sydekyks.com/getting-started/first-mission) uses the built-in Data Mapper.