degallery-overview

---
name: degallery-overview
description: Understand DeGallery's product model, choose the right JavaScript or React integration, and identify safe boundaries for uploads and media delivery. Use when planning or starting a DeGallery integration.
---

# DeGallery overview

DeGallery is a hosted media platform for uploading and organizing images, creating reusable galleries, and delivering or embedding them in applications. It separates the control plane (identity, organization/environment scope, metadata, authorization, billing, and policy) from media delivery (retrieval and storage access).

## Choose an integration

- Use `@degallery/sdk` for framework-neutral TypeScript clients in browser-safe public reads, server applications, workers, or other non-React integrations.
- Use `@degallery/node` for trusted Node.js code that also needs server helpers such as delivery-token signing. Do not bundle it into browser code.
- Use `@degallery/react` with `@degallery/sdk` and `@tanstack/react-query` to render galleries in React. It provides a provider, components, hooks, and gallery loading behavior.
- Use the REST API directly when a non-JavaScript service needs the API contract.

Prefer the smallest integration that fits the runtime. A browser app should not receive a private API key or delivery-signing secret.

## Core concepts

- Organizations and environments scope data and credentials. The server is responsible for resolving authorized scope.
- Assets are uploaded media records. Uploading uses a short-lived upload intent, transfer to its returned URL, then completion through the SDK/API.
- Galleries organize assets for public or authorized private presentation.
- Public and private media have different authorization requirements. A public key is restricted to published public content; private media needs a trusted server authorization path and short-lived delivery capability.

## Integration workflow

1. Choose the package for the runtime.
2. Create a client with the API URL and the least privileged credential appropriate to that runtime.
3. Upload assets through the intent, transfer, and completion flow when needed.
4. Read a gallery through the SDK or render it with the React package.
5. Keep private credentials and private authorization on a trusted server.

For details, use `degallery-javascript`, `degallery-react`, and `degallery-auth-and-private-media` as applicable. Consult the [integration choice guide](https://docs.degallery.dev/docs/guides/choose-an-integration) and [DeGallery developer docs](https://docs.degallery.dev) for current instructions. Confirm package APIs against the current published package documentation; do not assume roadmap or unverified provider features are supported.