Texbrain runs pdfTeX in-browser but hits standard citation walls

Solves a genuine problem for independent writers and researchers looking for a free, serverless editor.

The public static build works flawlessly for basic editing and compiling, as confirmed by Svelte stores and templates code.

WASM compilation is remarkably fast and functional, but relying on third-party proxies and external mirrors lowers long-term reliability.

Chromium user experience is smooth and fully integrated, though non-Chromium fallbacks are less intuitive.

Combines isomorphic-git, WASM pdfTeX, and File System Access in an inventive way that sidesteps backends entirely.

Active commits but single-maintainer bottleneck creates adoption risks for long-form papers.

Clear utility but limited by lack of compilation support for modern engines like XeTeX.

The core compiler, editor, and git logic are present, but there is no CI validation of the runtime WASM layer.

Well-structured client-side storage and memory file system, but fragile external HTTP dependencies lower the architectural rating.

Clean API definitions in Svelte stores, though error mapping from SwiftLaTeX WASM logs could be more structured.

Clever orchestration of existing tools like isomorphic-git and SwiftLaTeX, though the individual components are not new.

Single-person project with no automated regression testing visible, raising long-term stability concerns.

Particularly useful for writers looking for a clean, distraction-free environment without subscription limits.

The templates and snippet helpers are fully implemented and render cleanly in the UI.

Responsive state management via Svelte stores, providing smooth UI transitions and real-time log parsing.

Practically instant onboarding on Chromium. Clean templates speed up the first-run experience.

Bypasses the server entirely to solve the classical Overleaf payment wall, creating a clean, functional static tool.

Well-organized asset directories, but lacks clear UI accessibility benchmarks or localization support.

Academic utility is heavily compromised by the bibtex limitation, though excellent for basic documents.

Demonstrated through a fully operational GitHub Pages deployment and solid template configurations.

SvelteKit static build matches the serverless scope perfectly, minimizing deployment complexity.

Good command palette and shortcuts, but the non-Chromium experience falls short of the primary promise.

Addresses a very specific market gap between heavyweight local setups and expensive online subscription editors.

Clear listing of known limitations in the documentation shows strong, honest product stewardship.

High potential value for the open-source community, particularly users seeking privacy-focused alternatives.

Solid, functional codebase with a direct deployment flow, though lacking external testing validation.

The serverless compilation mechanics run pdfTeX entirely in-browser via WebAssembly, but the system lacks a fallback strategy if the primary WASM compiler repository goes unmaintained.

Zero-barrier access represents a major competitive advantage over traditional Overleaf setups.

Uses modern browser APIs to completely re-imagine what a collaborative LaTeX workflow looks like without server fees.

Good license and explicit limitations, but needs formal contributor guidelines and standard issue tracking to scale.