Supabase Native Vector Store & AI Assistant vs Together AI DeepSeek R2 Distilled Serverless Inference

“The primitive here is pgvector with managed HNSW indexing and a query interface that doesn't require you to know what ef_search is — that's the right DX bet, and they made it. The moment of truth is creating your first vector index from the table editor without opening a psql shell, and it survives that test cleanly. What earns the ship is that this isn't a wrapper — it's a first-class dashboard feature that replaces the five-step 'enable pgvector, create extension, run migration, configure index params, pray' workflow with a UI that makes the right choices by default without hiding the escape hatch.”

“The primitive here is clean: OpenAI-compatible serverless inference endpoint for distilled reasoning models, no infra to manage. The DX bet Together AI made is correct — zero-config model access with standard chat completions API means you swap one base URL and one model string and you're calling DeepSeek R2 distilled from existing code. The 32B at $0.80/M tokens is the real story: that's sub-dollar-per-million for a model that punches well above its weight class on reasoning benchmarks. The weekend alternative is self-hosting on RunPod or Modal, which works but adds cold-start latency, VRAM management headaches, and ops overhead that Together simply removes. Ship this if you're building anything that needs cheap chain-of-thought reasoning without the frontier model bill.”

“Direct competitors are Neon with pgvector, Pinecone for pure vector use cases, and PGVector.rocks for the self-hosted crowd — Supabase wins here on integration density, not vector performance. The scenario where this breaks is at scale: anyone running millions of embeddings with sub-10ms p99 latency requirements will hit pgvector ceiling before they hit a Supabase billing page. What kills the competition angle in 12 months isn't a competitor — it's Postgres itself shipping better vector primitives natively and Supabase simply keeping pace, which is actually fine because the SQL assistant is the real differentiator and nobody has shipped that as cleanly inside a dashboard.”

“Direct competitors are Fireworks AI, Groq, and Replicate running the same or similar distilled checkpoints — so Together is not selling exclusivity, they're selling reliability and price. The scenario where this breaks is high-concurrency production workloads where serverless cold-start variance becomes a latency SLA problem; Together's serverless tier has no guaranteed throughput contracts in the base offering. What kills this in 12 months is not a competitor but the underlying model provider: if DeepSeek ships R3 distills that are 2x better at the same cost, this specific offering goes stale and Together has to scramble to re-serve. That said, Together's track record of being early on new model availability is the actual moat here — they've consistently been first or second to serve hot open-weight checkpoints, and that speed-to-availability is worth paying for if you're iterating fast.”

“The buyer is the indie developer or small engineering team already on Supabase who just got a reason to never evaluate Pinecone — that's pure churn defense dressed up as a feature launch, and it's smart. The moat isn't the vector store, it's the switching cost: once your embeddings, auth, realtime, and storage live in one Postgres instance with one dashboard and one AI assistant that knows your schema, the activation energy to leave is enormous. The pricing holds because the AI assistant drives upgrade pressure naturally — free tier users hit complexity walls that the assistant solves on Pro, which is exactly the land-and-expand story that actually works.”

“The buyer is any developer or startup running LLM inference who currently pays OpenAI or Anthropic rates for reasoning tasks that don't require frontier-model quality — that's a real and large budget line item. The pricing architecture is usage-based and scales directly with value delivered, which is the right structure for inference. The moat question is harder: Together's defensibility is not the models (open weights, anyone can serve them) but latency, reliability, and the breadth of the model catalog creating switching friction once you've standardized your inference client on their SDK. The existential risk is that this is fundamentally a margin business on commodity compute, and Cloudflare Workers AI, AWS Bedrock, and Google Vertex are all moving to serve the same checkpoints at infrastructure-subsidized prices. Together needs to win on speed-to-new-models and developer experience before the hyperscalers catch up on catalog breadth, and so far they're doing it.”

“The job-to-be-done is 'ship a semantic search or RAG feature without standing up a separate vector database' and this product completes that job without requiring a second tool — that's the completeness bar and it clears it. Onboarding is strong: if you already have a Supabase project, the vector store is available immediately in the table editor and the AI assistant is already in the SQL editor, so time-to-first-embedding is measured in minutes not hours. The one gap is that the AI assistant's schema-awareness depends on how well-structured your schema is — if you inherited a legacy DB with undocumented tables, the assistant's explanations degrade fast, and that's a real workflow the product doesn't fully address yet.”

“The thesis Together AI is betting on: by 2027, the majority of production LLM inference will run on open-weight distilled models, not frontier APIs, because the quality gap closes faster than the price gap opens. That's a falsifiable and plausible claim — the DeepSeek R1 distillation story already validated it at the 7B-32B range. The dependency that has to hold is that distillation techniques keep pace with frontier capability jumps, which is not guaranteed if frontier labs accelerate architectural innovation faster than distillation pipelines can follow. The second-order effect that's underappreciated: cheap reasoning inference at this scale shifts power from model labs to inference infrastructure providers — Together, Fireworks, Groq become the AWS to the model labs' hardware vendors. Together is on-time to this trend, not early, but their execution on catalog breadth means they're well-positioned if the trend accelerates.”