I build Redexa Social, formerly Social Dashboard: a Windows desktop application for reviewing creator analytics in one workspace.
Its focus is analysis, not automated posting. It combines local analytics storage, trends and diagnostics, with CSV exports on Pro and Studio. The application uses a Python/FastAPI backend and an HTML, CSS and JavaScript interface.
Local-first does not mean offline-only
A useful distinction for an analytics product is where data is stored versus which services it needs to contact. Redexa Social keeps its analytics cache locally, but platform connections still communicate with provider APIs. Instagram and TikTok token exchanges can use a minimal remote OAuth proxy. Account authorization, billing, license verification and updates also involve remote services.
On Windows, credentials are protected at rest using DPAPI in the current user’s scope. This helps protect stored credentials, but it does not make them inaccessible to malware already running as that user.
Locally computed insights do not require calls to an AI model. That keeps those calculations separate from a hosted AI service.
What can you connect today?
Updated 20 October 2026.
- YouTube: direct connection is available.
- Instagram and TikTok: current use requires your own developer application, subject to provider requirements.
- X: credential status only; X analytics are not available.
The free plan supports one connected account and the core overview. CSV exports and full history require Pro or Studio.
That distinction matters: this is not yet a one-click connection experience for every platform. The application requests read-only analytics access; it is not a social publishing or scheduling tool.
Branding and package identity
Version 1.9.3 introduced the Redexa Social branding across the Windows shortcut, application icon and repository. The Windows executables distributed in the release are digitally signed and timestamped. The ZIP is a distribution container, not itself an Authenticode-signed executable.
Existing WinGet users should note that the package identifier remains AurelioAvila.SocialDashboard, even though the product is now called Redexa Social.
Try the current release
The project uses a proprietary license. Please check the repository license before reusing its code.
I would welcome feedback on the onboarding experience: is it clear which integrations work directly, which require developer setup, and where your data is stored? Please remove tokens, account identifiers and private analytics from any screenshots or logs you share.
Top comments (0)