Framework for SaaS applications

Cheap development and deployment

The whole app is implemented as a single Next.js application, that, when deployed, split into multiple serverless functions (smaller “back-ends”), each serving a specific purpose. This makes deployment infrastructure cheaper, having only one Next.js app to deploy with minimal configuration, while still being able to scale horizontally by adding more functions defined as Next.js page.tsx (UI) and route.ts (server-side code) files. The offering also makes development cheaper, as you don’t need to maintain monorepo with common UI and libraries, that require additional configuration, tooling, and planning in general.

Read more

• TODO: Next.js serverless functions
• Build Single Page Application

Enable multi-tenancy

In the most classical case a SaaS application is split into 3 “areas” or “tenants”:

1. Root area - serves landing page with some features like “subscribe to newsletter”, stats collection, etc. It’s available to all unauthenticated users serving marketing content, pricing plans, etc.
2. Customer area - serves authenticated paid or trial customers, providing access to the main features of the application.
3. Admin area - serves authenticated administrators, providing access to the admin features of the application, managing customer, billing, etc.

Each area is served from a separate Next.js route.ts file, allowing to split the application into multiple segments, each served as a separate Edge Function. This allows to scale the application horizontally by adding more functions, while still being able to serve different areas of the application from different domains, such as https://example.com, https://admin.example.com, https://customer.example.com, and so on.

Read more

• TODO nextjs routes
• More info about multi-tenancy

Enable AI features

TODO

Read more

• LLMs: AI SDK and JSONLines
• MCP server
• AI tools
• AI-powered client

Offer public API to your customers

Vovk.ts implements the conventional REST API, allowing to expose the API endpoints to the public without additional explanation. TODO

Read more

• TODO More info about API

Offer installable libraries for your public API

TODO

Read more

• OpenAPI code generation

Mix RPC library with other serverless

TODO

Read more

-OpenAPI code generation

Enable multi-tenancy

Split the app into multiple areas

Each area is going to have its own route.ts file, representing so-called segment in Vovk.ts that is served as a separate Edge Function:

• Root area is served from /api endpoint, implemented in src/app/api/route.ts file.
• Customer area is served from /api/customer endpoint, implemented in src/app/api/customer/route.ts file.
• Admin area is served from /api/admin endpoint, implemented in src/app/api/admin/route.ts file.

Each segment have its own set of controllers and services defined in src/modules/. The services are used to implement the business logic of the application (perform DB calls etc), while controllers define the API endpoints and their methods. Services can be shared between controllers as well as between segments, so you can implement the business logic once and use it in multiple places. For example, you can implement a service for the customer area that fetches the current user data and use it in both customer and admin segments.

SHARED LIB DRAWING TODO

Each controller of the segments automaticaly transformed into so-called RPC module, represented as an object that implements the same methods as the controller’s methods. The RPC modules can be imported from "vovk-client" package and used in the client-side code to call the API endpoints.

CODE TODO

MULTITENANT DRAWING TODO

Vovk.ts supports multi-tenancy out of the box, allowing to serve different areas of the application from different domains. This is achieved by using multitenant TODO function that processes the request information and returns the action to take, such as redirecting to a specific subdomain or rewriting the request to a different path.

Offer public API to your customers

The back-end framework implements the conventional REST API, allowing to expose the API endpoints to the public without additional explanation.

Offer installable libraries for your public API

xxxx

TypeScript

npx vovk bundle --out ./mylib

pnpm dlx vovk bundle --out ./mylib

yarn dlx vovk bundle --out ./mylib

bun x vovk bundle --out ./mylib

Vovk.ts provides TypeScript library bundler with auto-generated README.md and package.json files, allowing to publish the library to npm registry with npm publish command. Since the library uses fetch under the hood, it can be used in both Node.js and browser environments. Package name, description, and other metadata are taken from the package.json file in the root of the project and can be configured in the config file.

Rust and Python

Vovk.ts also provides support for generating Rust and Python libraries that can be used to call the API endpoints from the client-side code. The libraries are generated using the same vovk generate command, but with different flags for Rust and Python.

npx vovk generate --out ./mylib --from rs

pnpm dlx vovk generate --out ./mylib --from rs

yarn dlx vovk generate --out ./mylib --from rs

bun x vovk generate --out ./mylib --from rs

npx vovk generate --out ./mylib --from py

pnpm dlx vovk generate --out ./mylib --from py

yarn dlx vovk generate --out ./mylib --from py

bun x vovk generate --out ./mylib --from py

Implement AI-powered client

Coming soon.