MikeTrendsTrends right now
AI: reposAPI

search

SQLite

Trends

  1. 1
    Supabase raises $150M and acquires Turso●Database startup Supabase raises $150M, acquires Turso✉newsBusinessStartups1 h ago

    Open-source database startup Supabase has raised $150 million in new funding and announced the acquisition of Turso, a database company built on libSQL, a fork of SQLite. The funding will support Supabase's growth as demand rises for its Postgres-based backend platform used by developers building AI and web applications. The Turso deal strengthens Supabase's database technology stack and engineering team.

  2. 2
    Lightweight open-source database client DBX gains attention▼t8y2/dbx⬢github1.1K1 d ago

    A 25 MB open-source, cross-platform database client written in Rust is drawing attention for supporting more than 100 databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server and Chinese vendor Dameng. It ships as a desktop app, Docker image and CLI, and includes a built-in AI assistant and MCP server. Developers are discussing it as a lean alternative to heavier database management tools.

  3. 3
    Supabase is acquiring database startup Turso●Supabase is acquiring TursoYhn1734 h ago

    Supabase has announced it is acquiring Turso, the company behind the lightweight SQLite-based database platform. The news was published on Supabase's official blog and quickly drew attention among developers discussing consolidation in the database-as-a-service space. Details about deal terms and how Turso's technology will be integrated into Supabase's platform have not yet been made public.

  4. 4
    Developer details building an automated news pipeline with Flask and AI●Как я автоматизировала новостной поток: Flask, SQLite, AI и ошибки на пути к автопубликации Несколько месяцев назад я наMmastodonTechnologyAI02 d ago

    A developer has written up her experience building an automated news publishing system for an editorial team using Flask, SQLite and AI tools. The project aimed to free journalists from routine tasks so they could focus on reporting rather than manual publishing. She describes the technical setup and the mistakes made along the way to full auto-publication.

Repos