gitroomhq/postiz-app

This page introduces an external open-source repository. It is not an HDATF product.

What it does

Postiz is a social media management application for teams that need to coordinate publishing across multiple channels. It addresses the work of preparing posts, arranging publication times, and reviewing channel analytics in one place. Users supply post content, media, connected accounts, and a publishing schedule, and receive scheduled or published posts and available analytics. Team members can collaborate and comment, while the public API and documented MCP and CLI interfaces provide entry points for external automation. Its documented stack combines a NextJS interface, NestJS services, Prisma with PostgreSQL, and Temporal, and the development configuration also defines Redis and supporting services. Users can choose the managed cloud service or operate the open source edition on their own infrastructure, but the inspected development compose file explicitly is not a production configuration. Self hosting requires storage and environment configuration, developer applications and approval from social platforms, and external model credentials for optional AI features. Self hosting therefore does not remove platform API permissions, third party processing, or the operator's responsibility for updates, backups, and security.

License

AGPL-3.0 Network copyleft. Offering a modified version as a service also requires releasing the source. Review before any product use.

More in this category

• every-app/every-app
  EveryApp addresses the hosting, sign-in and permission work that remains after a coding agent creates an internal web application. It targets teams and developers who want to operate those applications in their own Cloudflare account. Inputs include an application definition, resource declarations and browser or AI tool requests, while outputs include a deployed application and authorized application results. A public Gateway checks access and forwards requests to private application Workers through internal connections, with signed identity verified at the application entry. The starter application scopes its database queries to the authenticated user's identifier, showing that row visibility remains the application's responsibility. Its tools declare separate read, write and destructive risk levels and are exposed to AI clients through the Gateway's MCP interface, a shared protocol for calling tools. Application declarations also specify allowed capabilities, while the Gateway keeps credentials and mediates external API access. The documented setup requires a Cloudflare account with Workers Paid and a Cloudflare managed domain, and the supplied stack uses Workers, D1, R2 and KV as applicable. The project explicitly remains in early development, so its access architecture is not proof of complete security, universal SaaS compatibility or production readiness.
• coollabsio/coolify
  Coolify is a self-hosted platform for deploying and managing applications and databases on your own servers. Operators connect Git repositories, container images, or Docker Compose configurations to manage builds, deployments, and runtime logs. Workflows include deployment on Git changes, preview environments, and rollback to retained images. It also manages domains, HTTPS, container networking, health checks, scheduled tasks, and backup settings. The inspected production Compose configuration separates persistent storage for the platform, database, and cache. Getting started requires a supported Linux server, SSH access, firewall preparation, and storage. After installation, administrators still connect accounts, repositories, environment variables, domains, and permissions; existing apps do not all migrate automatically. Self-hosting leaves platform and workload security, capacity, and backup recovery with the operator. Listed backup or rollback features do not guarantee complete restoration of every application's data, so recovery procedures require separate testing.
• warmbly/warmbly
  Warmbly is a self-hostable sales-email and mailbox-warmup platform for teams using mailboxes they already own. Users connect Gmail, Microsoft or SMTP and IMAP accounts and provide contacts, message sequences, timing and sending limits. It produces campaign records, opening and click events, replies, shared-inbox views and customer-management records. Mailbox warmup means gradually exchanging scheduled messages within monitored mailbox pools, not a guarantee that future mail reaches the inbox. The architecture separates state-owning Go backend and consumer services from interchangeable Go workers, with Postgres, Redis and an event bus, a React dashboard and a separate realtime service. Workers submit mail through each mailbox provider rather than delivering directly to recipients, and the default local stack uses NATS, local key management and filesystem storage. REST interfaces, webhooks and documented integrations support external connections, while AI functionality requires separate model-provider configuration. The documented start uses Docker Compose release images or a source build, then a one-time instance claim and mailbox connection, with OAuth application configuration needed for Google and Microsoft accounts. Development seeding shares the database with self-hosting and publishes demo administrator credentials, so production secrets, encryption-key backups and demo separation are essential; sending performance, inbox placement and ATF integration were not verified in this review.
• MapleTechLabs/maple
  Maple is a platform for developers and operators investigating service failures and slow requests. It accepts traces, logs and metrics through OpenTelemetry, a standard for collecting application execution data. Users can inspect request waterfalls, search logs and explore metrics together. Hosted MCP access also lets compatible AI clients query telemetry. Its local mode combines an ingest server, query API and dashboard in a Bun binary that loads the embedded ClickHouse library chDB. Starting locally requires a supported macOS or Linux bundle and its companion library, while sending data requires an instrumented application or collector. Local mode is single tenant, and an unclean shutdown can require restoring a checkpoint with loss of later telemetry. The current license is FSL-1.1-ALv2, which restricts competing commercial services and provides a future Apache 2.0 grant rather than unrestricted Apache licensing today.
• immortal71/openoncology
  OpenOncology is a research platform that combines tumor alteration evidence and ranks drug candidates for expert review, not a validated treatment recommendation service. Documented inputs include mutations, copy number changes and fusions, while the submission API accepts biopsy and DNA files with cancer type and requires patient authentication. Outputs include variants, evidence levels, source records and candidate drug rankings through separate results and repurposing APIs. The FastAPI server works with a Next.js interface, PostgreSQL, Redis, object storage and background workers, and the Docker configuration uses Python 3.11 and Node.js 20. Genomic processing has additional workflow and reference-data requirements, so starting the development containers does not establish that raw sequencing analysis will finish. Candidate scoring combines several evidence sources with renormalized weights, penalties and evidence-level rules, and its current configuration differs from an older README weight description. The default worker centers candidate generation on the first targetable mutation, so the whole-patient description should not be assumed to describe every execution path. Setup requires service secrets and configured evidence access, and unavailable OncoKB access can use a static fallback whose provenance limitations matter. Official documents retract an earlier circular oncologist-agreement evaluation, and the retrospective MSK CHORD comparison measures agreement with label-matched drugs rather than treatment benefit. The risk analysis states that clinical validation gates are unmet and results must not guide treatment, while this investigation only read sources and did not verify medical validity, performance or deployment readiness.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.