---
title: Overview
description: Add typed social platform features to a TypeScript application through direct integrations or optional managed backends.
---

Social SDK gives an application one typed model for connected accounts, content, media, publications, and destination outcomes. The selected account determines the integration route, and a failed request never moves to a different platform or account automatically.

## Start here

**[Install Social SDK](/getting-started/installation)**

Add the package and choose direct platform access or a managed backend.

**[Run the quickstart](/getting-started/mock-quickstart)**

Publish through a deterministic mock integration before adding credentials.

**[Understand the model](/concepts/integration-model)**

See how platforms, backends, content formats, and capabilities fit together.

**[Compare platforms](/platforms)**

Check the support matrix before choosing an adapter or operation.

## Choose an integration route

Choose a direct integration when you want to call a platform with credentials you control. Choose a managed backend when its account connection and operation coverage fit your application. Both routes keep credentials on the server and require the application to authorize every selected account for the current tenant.

**[Direct platforms](/platforms)**

Keep credentials and authorization in your application while calling a supported platform
directly.

**[Hosted platforms](/backends)**

Delegate account connections and supported operations to Zernio or Post for Me.

## Explore capabilities

**[Publish content](/publishing)**

Create content, attach media, publish to selected destinations, and inspect each outcome.

**[Read and measure](/reads)**

Read platform content and request analytics only where the integration exposes them.

**[Comments and messages](/comments)**

Work with supported comments, replies, and messaging operations.

**[Events and webhooks](/events)**

Verify inbound events and process them without hiding uncertain delivery outcomes.

**[Use your stack](/integrations)**

Wire the SDK into frameworks, databases such as Supabase and SurrealDB, and durable job runners.

**[Contribute an adapter](/contributing)**

Add a platform adapter with typed capabilities, fixtures, and honest evidence.

## Reference

**[API overview](/reference)**

Browse the public contracts and evidence for the SDK's operation model.

**[Capabilities](/reference/capabilities)**

Inspect the capability vocabulary used by adapters and support matrices.

**[CLI](/reference/cli)**

Find the command reference for project checks and local workflows.

**[Authentication](/authentication)**

Keep application authentication separate from social-account authorization.

:::note
Support is specific to a backend, platform, operation, content format, runtime, and evidence level. A provider's upstream feature is not treated as implemented or live-verified until Social SDK has matching code and evidence.
:::

The SDK does not provide a hosted social service, database, queue, credential proxy, scheduler worker, or billing layer. Applications supply platform or managed-provider credentials and choose the storage and job infrastructure they need.