ServicesSaaS MVPs


From idea to a working SaaS product in four to eight weeks, planned, designed and built by two engineers with 5+ years of production experience. You own the code from day one.

๐Ÿ•” 4 to 8 weeks๐Ÿ” You own the code๐Ÿค NDA on request
app.kryptos.io
Kryptos dashboard on desktop
Kryptos transactions on mobile

Real screens from Kryptos, the crypto tax and portfolio SaaS we've spent years building

5+

Years shipping production software

40,000+

People using a SaaS we helped build

50+

Third party integrations built and maintained

35+

Countries' financial data flowing through pipelines we built

โœ“AWS Certifiedโœ“EC-Council Certified Network Defenderโœ“SOC 2 aligned audit controlsโœ“Built a SaaS used by 40,000+ people

Who's actually building it?

We do. We're two engineers who've been shipping production software since 2019, and we're the only two people you'll work with ๐Ÿ‘‡

Shivanshu Pathak

Shivanshu Pathak

Cloud, security and DevOps ยท Shipping since 2019

Shivanshu builds the multi-tenant backends, data pipelines and cloud infrastructure a SaaS runs on, with security designed in from the start. Before Kryptos, Shivanshu built trading platforms at BW Labs, DeFi services at Mantle and a collaborative SaaS at Legora.

AWS CertifiedEC-Council CNDSecurity by design
AWSTerraformPostgreSQLDockerNext.js
Divyyesh Chandra

Divyyesh Chandra

Backend, integrations and AI ยท Shipping since 2022

Divyyesh builds the hard parts of financial software, like large third party integrations, event-driven pipelines and data systems that stay accurate at millions of records. Alongside that, Divyyesh designs and ships independent AI and real-time products, end to end.

50+ integrationsEvent-driven systemsAI products
TypeScriptNode.jsGoGCPLLM APIs

Where the experience comes from. Two careers, one story, starting in 2019.

2019

Legora

Collaborative SaaS

Real-time document editing, secure authentication and rate limiting, with backend APIs and analytics pipelines on AWS.

ShivanshuIngestion latency cut in half

2020

Mantle

DeFi platform

Cloud-native platform services in TypeScript, Node.js and GraphQL, built with the security team around auth and infrastructure as code.

ShivanshuGraphQL API 60% faster

2021

BW Labs

Trading systems

Backend platforms for financial trading built on event sourcing and audit trails, with real-time analytics on TimescaleDB, Redis and BullMQ.

ShivanshuIdempotent transaction processing

2022

DFrame

Data startup

The Reward Engine end to end, from Kafka and MongoDB pipelines to the React app, the KYC and referral APIs and the reward contracts.

DivyyeshOwned it through to production

2023

Kryptos

Crypto tax SaaS, 40,000+ users

50+ integrations, event-driven pipelines on GCP, multi-tenant PostgreSQL with SOC 2 aligned controls, and AWS infrastructure written in Terraform.

Shivanshu and DivyyeshPlatform uptime up 15%

Now

Nexussstudio

Our studio

Everything above, pointed at your product. We plan, design and build SaaS MVPs, online stores and websites for founders.

Shivanshu and DivyyeshYour MVP could be next

Have they built a real SaaS?

Yes. We've both spent years building Kryptos, a crypto tax and portfolio SaaS used by 40,000+ people in 35+ countries. These are real screens from it ๐Ÿ‘‡

Plug in every exchange and wallet

This is where people connect their accounts. Behind this list sit the 50+ integrations we built, syncing quietly in the background.

Plug in every exchange and wallet

Every trade in one list

Deposits, rewards and trades from every connected account end up here, cleaned up, priced and ready for the tax report.

Every trade in one list

Works properly on a phone

The whole app works on mobile, not a cut down version of it. The portfolio, the tax tools and the reports are all there.

Works properly on a phone

On desktop

Where the numbers have to be right

Every row here comes in through the integrations and pipelines we built. If one number is wrong, it ends up in someone's tax report. That's the standard we hold every system to, including yours.

app.kryptos.io
Kryptos transactions table on desktop
Divyyesh

50+ integrations, one schema

We owned the layer that connects 50+ exchanges, platforms and blockchains, and a normalisation layer that turns every source into one clean schema.

Divyyesh

Event-driven pipelines

An event-driven backend on Google Cloud Pub/Sub and Cloud Tasks, with automated anomaly detection running across millions of records.

Shivanshu

Multi-tenant and secure

Multi-tenant modules with PostgreSQL row-level security and audit controls aligned with SOC 2, so one customer never sees another's data.

Shivanshu

Data from 35+ jurisdictions

Automated ingestion pipelines that pull in financial transaction data from more than 35 jurisdictions and keep it consistent.

Divyyesh

Firebase to PostgreSQL

We led the move from Firebase to a Turborepo monorepo on PostgreSQL, shipped through zero-downtime CI/CD on Docker, GitHub Actions and Cloud Run.

Shivanshu

Uptime up 15%

Cloud deployments on AWS written as Terraform, plus automated failover, observability and monitoring that lifted platform uptime by 15%.

How will you build my MVP?

The same way we build production software. We plan it, design the system, design the screens, then build, test and launch it ๐Ÿ‘‡

A typical eight week MVP

Shorter scopes finish in four

12345678

Plan

System design (HLD)

Detailed design (LLD)

UI design

Build

Test

Launch

Demo

โ–ถโ–ถโ–ถโ–ถ
01

Plan

We start with your users, not the tech. On the first calls we write the user stories, cut the idea down to a first version and agree the milestones.

You get Scope and fixed quote

02

System design (HLD)

We draw the whole system before writing any code, including the services you need, how data moves, which cloud it runs on and which third parties plug in.

You get Architecture diagram

03

Detailed design (LLD)

Then we go a level deeper into the database schema, the API contracts, roles and permissions, and the edge cases that usually only show up in production.

You get Schema and API spec

04

UI design

We design the key flows in Figma and turn them into a clickable prototype, so you can click through the product before it's built.

You get Figma prototype

05

Build

We build in two week sprints and show you working software at the end of each one. There's no big reveal at the end and no surprises.

You get A demo every two weeks

06

Test

Unit, integration and end to end tests run on every change, along with a security review of auth, data access and payments.

You get Tests and security checklist

07

Launch and hand over

We set up CI/CD, infrastructure as code and monitoring, launch on your domain and hand over the code, the docs and every login.

You get Live product you own

What does the system look like?

Before any code, we draw it. First the high level design, then the low level design. Here's what that looks like for a typical SaaS ๐Ÿ‘‡

High level design

This is the big picture. It shows every service, how they talk to each other and where the data lives.

Clients

Web appNext.js
Admin panelReact
Mobile webResponsive

Edge

CDN and WAFCaching and protection
API gatewayAuth checks and rate limits

Services

AuthOAuth, roles, sessions
Core APINode.js or Go
BillingStripe
WorkersGo or Python jobs

Events

QueuePub/Sub, SQS or Kafka
SchedulerRetries and cron jobs

Data

PostgreSQLRow-level security
RedisCache and rate limits
File storageS3 or Cloud Storage

Around everything

CI/CDGitHub Actions
Infra as codeTerraform
ContainersDocker
MonitoringLogs, metrics, alerts

Low level design

This is where it gets detailed. It covers the tables, the API contracts and the rules that keep your data safe.

Database schema

organizations

id uuid pk

name text

plan text

created_at timestamptz

users

id uuid pk

org_id uuid fk

email citext unique

role owner | admin | member

subscriptions

id uuid pk

org_id uuid fk

stripe_id text

status active | past_due

audit_logs

id bigint pk

org_id uuid fk

actor_id uuid fk

action text

users, subscriptions and audit_logs all belong to one organization

// API contract, agreed before we build

POST /v1/projects

Authorization: Bearer <token>

Idempotency-Key: 7c1eโ€ฆ

{ "name": "Q3 launch" }

201 Created

{ "id": "prj_8f2k", "orgId": "org_12" }

โœ“Row-level security on every tenant table

โœ“Idempotency keys on payments and webhooks

โœ“Rate limits per user and per organisation

โœ“Every change written to the audit log

This is an example. Yours gets drawn around your product in the first week, and you get to keep it.

What do you build with?

We use tools we've run in production for years, not ones we picked up for this page ๐Ÿ‘‡

Cloud and DevOps

AWS
Google Cloud
Terraform
Docker
GitHub Actions
GitHub

Backend

Node.js
TypeScript
Go
Python
Express
GraphQL

Data

PostgreSQL
Redis
Kafka
MongoDB
Supabase
Firebase

Product

Next.js
React
Tailwind CSS
Figma
Stripe
Vercel

What goes into it?

Everything a first version of a SaaS needs, built properly the first time ๐Ÿ‘‡

The core product

The dashboards and flows your users came for, designed and built together so they feel like one product.

Active users

2,418

MRR

ยฃ8.2k

Churn

1.9%

Sample data

Sign up and accounts

Email, Google and Apple sign in, with sessions and password resets handled properly.

Create your account

Continue with GoogleContinue with Apple
Continue

Billing from day one

Plans, trials and subscriptions through Stripe, so you can charge your first customer.

Plans

MonthlyYearly

Starter

ยฃ19/mo

Pro

ยฃ49/mo

Payments, trials and invoices through Stripe

Teams and roles

Invite teammates, set roles and keep every organisationโ€™s data apart.

Team

Invite
MMaya ChenOwner
TTom ReeveAdmin
AAva PatelMember

Emails and alerts

Welcome emails, receipts and in-app alerts that go out at the right moment.

Welcome email sentJust now

Plugged into the tools you already use

Payments, cloud storage, analytics and the APIs your product depends on, wired in and tested.

API

Is this for me?

(01)

Non technical founders

You have the idea and the customers. You need a product people can actually use.

(02)

Founders validating a SaaS

You want paying users on a real product before you raise or hire a team.

(03)

Teams testing a new idea

A focused first version to put in front of users before you hire a full team.

โœ“

Fixed price per milestone

You know the full cost before we start. No hidden fees.

โœ“

You own everything

The code, the design and the IP are yours outright. NDA if you want one.

โœ“

Quick to start

Kickoff usually happens within a week of our first call.

Any questions left?

  • A focused MVP usually takes four to eight weeks. We'll give you a clearer timeline once we've scoped the first version together.

What else do they do?

Got a SaaS idea? Let's scope it.

Book a free 30 minute call with both of us. We'll sketch the first version with you and quote a fixed price per milestone.