Velt Self Hosting Data Best Practices

|v1.0.0|Velt|March 2026 |IMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning for any Velt tasks. |IMPORTANT: VeltProvider requires the authProvider prop for authentication. Do NOT use the deprecated useIdentify hook or client.identify(). Pattern: <VeltProvider apiKey={KEY} authProvider={{ user: { userId, organizationId, name, email }, retryConfig: { retryCount: 3, retryDelay: 1000 }, generateToken: async () => { /* fetch from /api/velt/token */ } }} dataProviders={dataProviders}>. Data providers must be set on VeltProvider BEFORE authentication occurs. |root: ./rules

1. Core Setup — CRITICAL

|shared/core:{core-auth-provider.md,core-provider-setup.md,core-response-format.md,core-python-sdk-setup.md}

2. Comment Data Provider — HIGH

|shared/comment:{comment-endpoint-provider.md,comment-function-provider.md}

3. Attachment Data Provider — HIGH

|shared/attachment:{attachment-multipart-provider.md}

4. Additional Providers — MEDIUM

|shared/provider:{provider-reaction-recording.md,provider-retry-timeout.md,provider-user-resolver.md,provider-notification.md,provider-recorder.md}

5. Backend Implementation — MEDIUM

|shared/backend:{backend-database-patterns.md,backend-s3-attachments.md,backend-api-routes.md}

6. Data Types — MEDIUM

|shared/data:{data-types-reference.md}

7. Python SDK (velt-py) — HIGH

|shared/python-sdk:{python-comments.md,python-attachments.md,python-users-reactions.md,python-frameworks.md}

8. Debugging — LOW-MEDIUM

|shared/debug:{debug-data-provider-events.md}