Deploy your code. We’ll handle the infrastructure.
One project. One platform. Everything your application needs.
LLMs have made software development dramatically faster. Deploying an application still means dealing with databases, storage, compute, networking, and the infrastructure underneath.
Nyas simplifies that layer. Through a consistent CLI and MCP interface, developers and coding agents can provision PostgreSQL, object storage, and application infrastructure in minutes.
We’re using Nyas to power Formulate AI. Try it for your next project.
See the setup stepsYour application, and the services it depends on, live in a single project. They are provisioned together, billed together, and reach each other without any wiring.
Grouped by what's ready to use today.
Application deployments from Git or a Dockerfile. Nyas detects the runtime, builds a container, and serves it over HTTPS on a generated domain or your own.
Deployment docs
A production-ready relational database. Unmodified
PostgreSQL 18 with pgvector,
postgis and pg_trgm
pre-installed. Your ORM, your SQL, your
pg_dump.
S3-compatible buckets with generated access keys. Existing S3 SDKs, the AWS CLI, and presigned URLs work unchanged.
Explore StorageManage every resource programmatically. One REST API, one CLI, and an MCP endpoint for coding agents. The dashboard has no powers they do not.
See the interfacesRun code close to your users. Short-lived functions deployed from the same project as your application.
Not available yetA fast cache and message broker for sessions, rate limiting, and background jobs.
Not available yet
Semantic search for AI applications. Until it ships,
pgvector is available on every Nyas
Postgres database today.
Users, OAuth, API keys, and JWT, wired into your project's database.
Not available yetMost of the building blocks here exist on every other platform. These are the six choices that don't.
Unmodified PostgreSQL 18. Your ORM, your
extensions, and pg_dump all work
exactly as they do anywhere else.
Existing S3 SDKs, the AWS CLI, and presigned URLs work unchanged — no proprietary upload API to learn.
Your app, database, and storage share a project and a single invoice — not three vendor consoles and three renewal dates.
Whatever your account can do, all three interfaces can do. Nothing on the platform is dashboard-only.
Pay for the compute, storage, and bandwidth you use. No per-seat pricing and no per-query metering.
pg_dump and standard S3 tooling work
in both directions. Nothing is locked to a
proprietary export format.
git pushThe same four steps whether you deploy from the CLI, from a Git push, or from an agent calling the API.
Connect a repository or run
nyas deploy from your working
directory.
The runtime is detected and a container image is built. No Dockerfile required.
The new revision passes health checks and takes traffic while the old one drains. Served over HTTPS with a managed certificate.
Add compute, read replicas, and storage as traffic grows. No rewrite required.
Use the CLI, the REST API, or point a coding agent at our MCP endpoint. Same surface, same permissions, same results.
# Create a project with Postgres and object storage curl -X POST https://api.nyas.io/v1/projects \ -H "Authorization: Bearer $NYAS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "acme-api", "region": "ap-south-1"}' # Read the credentials it generated curl https://api.nyas.io/v1/projects/$PROJECT_ID/credentials \ -H "Authorization: Bearer $NYAS_API_KEY"
# Register Nyas as an MCP server, then ask in plain English: # "Create a project with Postgres and storage for this app." { "mcpServers": { "nyas": { "command": "nyas", "args": ["mcp"] } } }
Use the CLI for terminal workflows or local MCP clients. Remote HTTP MCP clients can connect without installing it.
Choose one installer for your environment.
macOS / Linux
curl -LsSf https://app.nyas.io/install.sh | shWindows PowerShell
irm https://app.nyas.io/install.ps1 | iexnpm alternative
npm install -g @formulateai/nyasSign in
nyas loginCreate a project and deploy
nyas start
nyas sql <project-id>
nyas deploy .
nyas start provisions PostgreSQL and
prints its connection URI. The SQL command opens
a REPL for an existing project.
For remote MCP, use
https://api.nyas.io/mcp. These clients
can authenticate with OAuth; other remote clients
can use a bearer token.
Codex
codex mcp add nyas --url https://api.nyas.io/mcpClaude Code
claude mcp add --transport http nyas https://api.nyas.io/mcp
For a stdio-only client, install the CLI, run
nyas login, and configure the local
nyas mcp command. Restart the client
after login.
Local MCP JSON
{
"mcpServers": {
"nyas": { "command": "nyas", "args": ["mcp"] }
}
}Local MCP TOML
[mcp_servers.nyas]
command = "nyas"
args = ["mcp"]No fork, no dialect. Your ORM already supports it.
Existing SDKs, the AWS CLI, and presigned URLs work as-is.
Managed certificates issued and renewed for every domain.
Point-in-time recovery on paid plans, retained 7–14 days.
On every deployment, with no agent to install.
Session and transaction modes, for serverless and edge clients.
Whatever you're building, there's a good chance it looks like one of these.
If it isn't here, email manish@nyas.io. You'll hear back from a human, usually the one who wrote the code.
Available today: application deployments, managed PostgreSQL, S3-compatible object storage, and the API and CLI that drive them. You can sign up and use all of it right now.
In development, not available
yet:
Edge Functions, Redis, Vector Database, and
Authentication. These appear on the platform
overview marked coming soon so you
can plan around them, but there is nothing to
provision today. If you need a vector store
now, pgvector is pre-installed
on every Nyas Postgres database.
It's unmodified PostgreSQL 18. No proprietary dialect, no custom client library, no Nyas-specific schema to learn. Your existing ORM (Prisma, Drizzle, SQLAlchemy, GORM, ActiveRecord, anything that speaks Postgres) works without changes.
Standard tools like pg_dump and
pg_restore work normally, which
means you can leave whenever you want.
Every Nyas database comes with the following extensions pre-installed and ready to use, no extra setup required:
| Extension | Purpose |
|---|---|
fuzzystrmatch |
Fuzzy string matching: Soundex, Levenshtein, Metaphone |
hstore |
Key-value pairs stored in a single column |
ltree |
Hierarchical tree-like data: labels, paths, ancestry queries |
pg_graphql |
GraphQL support directly inside PostgreSQL |
pg_stat_statements
|
Query performance statistics |
pg_trgm |
Trigram-based fuzzy text search and similarity scoring |
pgcrypto |
Cryptographic functions: hashing, encryption, UUID generation |
plpgsql |
PL/pgSQL procedural language for stored procedures and triggers |
postgres_fdw |
Foreign data wrapper for querying remote PostgreSQL databases |
tablefunc |
Cross-tab queries and other table-function utilities |
uuid-ossp |
UUID generation functions |
Yes. Nyas provides a built-in proxy that supports both connection pooling and transaction pooling modes, useful for serverless functions, edge runtimes, and apps that open many short-lived database connections.
Your pooled connection string and proxy settings are available in your project dashboard. Use the direct connection string for long-running processes (background workers, migrations) and the pooled connection string everywhere else.
Remote MCP clients can connect directly to
https://api.nyas.io/mcp using
OAuth or a bearer token; no CLI install is
required. For Codex, run
codex mcp add nyas --url https://api.nyas.io/mcp.
For Claude Code, run
claude mcp add --transport http nyas https://api.nyas.io/mcp.
For local stdio clients, install the CLI,
run nyas login, then configure
command nyas with args
["mcp"]. See the
setup steps.
For simpler workflows, paste the standard
Postgres connection string and storage
credentials into your agent's environment or
.env file. Use
DATABASE_URL for SQL and the
S3-compatible endpoint, bucket, access key,
and secret key with normal S3 SDKs. The MCP
path lets agents create projects, run SQL,
inspect schemas, get credentials, and manage
storage. See the examples repo for full
workflows:
github.com/nyastech/nyas-examples.
Yes, both directions, using standard Postgres and S3-compatible tooling.
In:
pg_restore from a dump, or
\copy from CSV, or logical
replication from an existing Postgres.
Out:
pg_dump against your Nyas
connection string gives you a portable SQL
dump you can restore anywhere else. For
storage, use any S3-compatible CLI or SDK to
copy objects in or out of your bucket.
There's no proprietary export format and no lock-in layer. If Nyas stops being the right fit for you, you can leave in minutes.
You get a warning email before anything is throttled or paused. We don't auto-charge a card you haven't given us. You decide whether to upgrade to Starter, clean up data, or wait.
Free tier limits today: 500 MB database, 1 GB file storage, 2 projects, 1 GB egress per month.
Yes. Paid plans can be paid in INR through RazorPay, which means UPI, Indian credit cards, net banking, and wallets all work. USD billing is also available if you're outside India or expensing to an international card.
Annual billing gets you 20% off. There are no per-query or per-operation charges, so your bill won't spike from a runaway loop. Overages on storage and egress are billed at a fixed rate per GB (₹10 / $0.09).
Backups: Daily automated backups on Starter (7-day retention) and Growth (14-day retention). Free tier is best effort, so do not rely on it for anything you cannot rebuild.
Uptime: 99.9% SLA on paid tiers.
Support: Community Discord for free, email for Starter, priority WhatsApp/Slack for Growth.
If something breaks: Email manish@nyas.io or open an issue at github.com/nyastech/nyas-examples/issues. We're a small team, you'll hear back from a human, usually the one who wrote the code.