Test your API, your UI, and your database in one tool

When you're debugging a bug, you usually need three windows open: your API client, your browser, and a database GUI. You send the request, watch the response, check if the database updated correctly, then reload your UI to see if the UI reflects the change. It's a workflow loop that every developer knows. Rostyman is the first tool designed to close that loop — API testing, browser automation, and a database client, all in one window.

Why three separate tools slow you down

Context-switching between apps has a cost that's easy to underestimate. Every switch resets your mental stack. You tab out of your API client, wait for the database GUI to wake up, navigate back to the table you were looking at, then switch to the browser to run the test — and now you've forgotten which assertion failed. Integrated tooling isn't just convenient. It's a cognitive advantage.

There's also the practical issue of shared state. An API test that sets an environment variable should be visible to the database query you run next. A browser test that fills a form should be validated against the database row it creates. When these tools are separate applications, sharing state requires manual copy-paste. In Rostyman, it's native.

What API testing looks like today

Rostyman's API layer is fully built and shipping. Eight protocols: HTTP/REST, GraphQL, gRPC, WebSocket, Socket.IO, MQTT, SSE, and MCP. Every protocol supports auth, scripts, history, environments, and collections. The scripting API is rm.* — rm.environment.get(), rm.test(), rm.expect() — familiar if you've used any modern API client, but running entirely locally with no cloud execution.

The visual workflow editor lets you chain requests into multi-step flows — auth token fetch, conditional branching, transform steps, retry logic — without writing orchestration code. The AI assistant (OpenAI, Anthropic, or local Ollama) can generate requests from plain English, explain responses, and write test assertions.

The database layer (coming soon)

The database client is on the roadmap. Seven databases at launch: PostgreSQL, MySQL, SQLite, MongoDB, Redis, ClickHouse, and DynamoDB. The key feature that differentiates it from standalone tools like TablePlus or DBeaver is Linked Contexts — you can bind a database connection to a collection, and your pre-request scripts can query the database directly: rm.db.query('SELECT * FROM users WHERE id = ' + userId). Validate the API response against the actual database state, in one script, in one window.

The browser layer (coming soon)

The browser automation layer uses embedded Chromium via the Chrome DevTools Protocol — no Playwright or Puppeteer config files required. Performance profiling, WCAG accessibility audits, visual regression testing, and AI test generation are all planned. The assertDB step lets you bind a database connection to a browser test and validate that a UI action produced the expected database change — closing the loop between the three layers entirely.

Today

The API layer is available now, free, no account required. The database and browser layers are on the roadmap. In the meantime, even with just the API layer, the workflow editor, and the AI assistant, Rostyman handles most of the work developers reach for a standalone API client or scripting tool to do. That's enough to start with.