A decentralized, open-source writing platform that permanently stores your stories on the Stacks blockchain and Arweave — where Web3 content creators own their words forever.
Sigle is a secured and open-source writing platform built for Web3 content creators, NFT project teams, crypto analysts, and independent writers who want true ownership of their published work. Rather than storing posts in a centralized database, Sigle anchors every published article on the Stacks blockchain and stores the full content on Arweave, giving authors permanent, censorship-resistant storage that no platform can delete or paywall.
The editor experience is powered by TipTap and delivers a modern, distraction-free writing environment with slash commands, code block syntax highlighting, image uploads, tweet embeds, cover images, and markdown support. Writers compose in a familiar rich-text interface while the platform handles the complexity of blockchain transactions transparently in the background — showing a multi-step progress toast as their draft moves from Arweave upload through Stacks transaction confirmation to indexing.
Beyond writing, Sigle functions as a complete publishing ecosystem. Each author gets a public profile page, custom domain support, and an RSS feed. Readers can browse trending posts and discover creators through an explore page. The platform also supports NFT-gated content collection, letting writers monetize specific stories by minting them as on-chain collectibles that readers can claim.
The entire project is structured as a Turborepo monorepo with a Next.js 16 front-end, a Nitro-based API server backed by PostgreSQL via Prisma, Clarity smart contracts on Stacks, an SDK package for contract interaction, and a custom-domain service. Docker Compose orchestrates the full stack for local development.
Architecture Sigle is organized as a Turborepo monorepo that cleanly separates concerns across distinct workspaces: a Next.js application for the user-facing front-end, a Nitro-based HTTP API server, a shared TypeScript SDK that encapsulates Stacks contract interaction and OpenAPI-typed API clients, Clarity smart contracts for the Stacks blockchain, and a lightweight custom-domain proxy service. The front-end communicates with the API exclusively through a typed OpenAPI client generated from the server’s schema, eliminating runtime type mismatches between layers. The publishing pipeline follows a strict multi-step transaction model — draft data is first uploaded to Arweave via IPFS-compatible CID computation and an S3-compatible storage backend, then a Stacks contract call registers the content hash on-chain, and a background job indexer polls for confirmed transactions and writes the indexed post into PostgreSQL. This event-driven indexing approach keeps the database consistent with on-chain state rather than trusting optimistic writes.
Tech Stack The front-end is built on Next.js 16 with React 19, using Tailwind CSS v4, ShadCN UI components, and TipTap v3 as the rich-text editor with extensive extension plugins including lowlight syntax highlighting and a custom slash-command system. Authentication is handled by better-auth with Sign-In-With-Stacks (SIWS), a wallet-based authentication standard that ties user sessions to Stacks addresses. The API server runs on Nitro, backed by PostgreSQL accessed through Prisma v7, with pg-boss handling background job queues. On-chain interactions use the Stacks.js SDK and Clarity smart contracts that implement NFT post minting, fixed-price sales, and protocol registry logic. Content is stored on Arweave through ArDrive’s Turbo SDK, with CIDv1 fingerprinting via the multiformats library ensuring content integrity between the client-computed hash and the server-confirmed CID. Monitoring is handled by Sentry on both client and server, and product analytics use PostHog.
Code Quality The codebase demonstrates strong quality discipline. TypeScript strict mode is enforced project-wide and the SDK generates its types directly from the OpenAPI schema, ensuring the API contract is the single source of truth. Error handling follows a Railway-oriented pattern using the better-result library, giving explicit typed Result types rather than thrown exceptions in async paths — this is consistent across the Stacks API client, contract calls, and job indexers. Testing coverage is comprehensive in the server and SDK layers, with test files for route handlers, job indexers, metadata parsers, and contract interaction logic, using PGlite (an in-process PostgreSQL engine) for database tests that avoid mocking. The front-end includes editor component tests with Testing Library. Linting uses oxlint with a custom plugin for Tailwind, and formatting uses oxfmt, both enforced in CI. The monorepo uses Turborepo with remote caching for efficient builds.
What Makes It Unique Sigle occupies a genuinely novel position: it is a fully functional blogging platform where the persistence layer is a public blockchain and a permanent content-addressable storage network, yet the authoring experience is as polished as a mainstream CMS. The key technical differentiator is the CID-verified Arweave pipeline — the client computes an IPFS CIDv1 from the serialized post content before upload and the server validates the returned CID matches, providing end-to-end content integrity guarantees without trusting the storage provider. The NFT collection mechanism is implemented through Clarity smart contracts with fixed-price minting, meaning creators can monetize specific posts as on-chain collectibles with verifiable scarcity. The Sign-In-With-Stacks authentication eliminates passwords entirely, anchoring user identity to a blockchain wallet, which is a meaningful departure from both traditional credential systems and OAuth-based social login.
Sigle is released under the MIT License, which is one of the most permissive open-source licenses available. You are free to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software without restriction. There are no copyleft implications — you are not required to open-source any modifications you make, and you can use Sigle commercially without paying licensing fees or obtaining special permission. The only requirement is that the MIT copyright notice be included in copies or substantial portions of the software.
Running Sigle yourself requires operating several interconnected services simultaneously. The monorepo includes a Docker Compose configuration that covers a PostgreSQL database, the Nitro API server, the Next.js front-end, and the custom-domain proxy. Beyond the application tier, you will need an S3-compatible object storage bucket configured to act as an IPFS-pinning proxy (the server uploads content and expects a CID returned in the response headers), access to the ArDrive Turbo service for Arweave uploads, and a Stacks node or a reliable Hiro API endpoint for transaction submission and confirmation polling. You are also responsible for managing Prisma database migrations, rotating secrets, monitoring background job queues (pg-boss), and handling Sentry error ingestion if you want observability. This is a multi-service deployment with meaningful operational overhead compared to a simple single-container app.
The hosted version at sigle.io handles all of this infrastructure on your behalf, including Arweave storage costs, Stacks RPC reliability, database management, and deployment. Self-hosters give up managed upgrades, the hosted Arweave gateway integrations, and any support SLAs the team provides to hosted users. There is no published distinction between a free self-hosted tier and a paid cloud tier — the codebase is fully open, so feature parity is complete — but the operational complexity of coordinating blockchain, permanent storage, and traditional database layers means self-hosting Sigle is best suited to teams with infrastructure experience rather than individual writers looking for a simple setup.
Developer Tools · Blogging · CMS
The open-source, Next.js-native headless CMS that lives inside your /app folder and gives you a full TypeScript backend instantly.
Marketing · Blogging
High-performance, self-hosted newsletter and mailing list manager packaged as a single binary with built-in analytics, transactional messaging, and multi-channel delivery.
Ecommerce · Blogging · CMS
Open-source, self-hosted CMS on AWS serverless — a TypeScript framework you extend with code, not a product you configure through a UI.