SPYN3 is AI-ready data infrastructure for technical solopreneurs and AI builders. It connects business sources into a workspace-isolated knowledge layer and exposes that layer through a REST API and hosted Model Context Protocol server, with permission-scoped access and source records attached to retrieval. SPYN3 is currently in private beta.
The problem SPYN3 solves
Business knowledge is spread across files, websites, databases and SaaS tools. A new assistant or automation often causes a team to rebuild ingestion, chunking, indexing, retrieval and access control for data it already connected elsewhere. SPYN3 turns that repeated project work into a reusable infrastructure layer.
The first useful result is simple: connect a real source, ask a question, inspect the supporting records, then give an external agent access to the same workspace without building a second data pipeline.
How the system works
Files, public pages, Postgres and configured application connectors.
Source content becomes a consistent internal model.
Semantic and keyword retrieval operate inside one workspace.
Workspace and credential scopes are enforced before access.
Agents and applications use the same knowledge layer.
Two interfaces over one dataset
An MCP-capable agent discovers a small set of search, answer, source and detail tools on the workspace endpoint.
HTTP applications call query, search, source and tool endpoints with the same workspace-scoped machine identity.
The human setup surface creates workspaces, connects sources, monitors sync and issues credentials.
Both machine interfaces use the same indexed documents, response policy and provenance records.
Implementation details and examples live in the SPYN3 developer documentation.
Security and control model
- Every document, connector and machine credential belongs to a workspace boundary.
- Postgres row-level security adds a database-level tenant boundary behind application checks.
- API-key secrets are stored as hashes; connector credentials are encrypted at rest.
- Machine access is explicitly permission-scoped and independently revocable.
- Agent-facing list and retrieval calls are bounded rather than returning entire collections by default.
- SPYN3 does not replace the client's prompts, approval UI or domain review.
Current availability and boundaries
SPYN3 is onboarding technical builders through a private beta. Invitations, hosted origins, credentials and enabled connectors are supplied during onboarding; general-availability pricing and service commitments have not yet been announced.
SPYN3 is infrastructure, not a general chat assistant, visual agent builder or workflow-automation suite. Durable agent memory and inbound MCP federation are product directions, not claims about the current beta surface.
Name and canonical identity
The product name is SPYN3, written in capitals and pronounced “spine.” Its canonical public website is spyn3.com. The retired domain use-spine.com redirects to the canonical SPYN3 URL and is not a second product.
Use the canonical definition at the top of this page when identifying SPYN3. Product mechanics on this page describe the current private-beta implementation; roadmap items are labeled separately. Machine-readable summaries are available at llms.txt and llms-full.txt.
Connect the data once
Make the next agent the easy one
Bring a real business source and a recurring agent question. SPYN3 supplies the reusable context layer; you retain control of the agent and the decision it supports.
Request private beta access