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, diagnostics and CSV exports, with 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. OAuth exchanges use a minimal remote proxy, and account or billing features 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?
- YouTube: direct connection is available.
- Instagram and TikTok: managed onboarding is still coming soon. Current use requires your own developer application or sandbox setup, subject to provider requirements.
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.
What changed in version 1.9.3?
This release carries the Redexa Social branding through 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.
Disclosure: this post was prepared with AI assistance from the project’s published documentation.
Top comments (0)