Storing processed API request metadata for analytics dashboards, Replacing vector databases for standard full-text keyword search (BM25)
It is a foundational database layer that can directly serve as a REST API, eliminating the need for a separate backend.
Users are unclear if it's an alternative to or a wrapper for PostgREST for the API layer
Reviews from businesses like yours — matched by size and type. Available once you create a profile.
Complete profileRelated Tools
Community Reviews
Reviews from Reddit, Product Hunt, Hacker News & AlignAI members
Check processed_events for event.id Insert event.id before side effects
Hacker News • HackerNews • Use case: Storing processed event IDs for idempotency checks
Ingestion is decoupled from the dashboard. SDKs POST to a standalone Go ingest service (ingest.peekapi.dev) that handles geo extraction, batching, and writes to Postgres.
Hacker News • HackerNews • Use case: Storing processed API request metadata for the analytics dashboard
Postgres with Drizzle ORM.
Hacker News • HackerNews • Use case: Used as the database.
This build is running on top of Postgres + Redis + RabbitMQ + S3 + an LLM router (20+ providers).
Hacker News • HackerNews • Use case: As a foundational database layer for their AI substrate/operating system.
Now, when a user searches, we hit Postgres first. It costs $0 in API fees and takes 50ms.
Hacker News • HackerNews • Use case: Replacing the vector database for standard full-text keyword search (BM25).
Smith uses Postgres row level security to isolate user agent interactions and provides Postgres based session storage that the agent can query with full-text search.
Hacker News • HackerNews • Use case: Session storage and row-level security for user agent isolation
Is this offering an alternative to PostgREST or a wrapper around it?
Hacker News • HackerNews • Use case: Considering it as a potential alternative for the API layer
Have You Used This Tool?
Sign in to share your experience with this tool.
Sign in