Projects

Case studies that explain what we built and why the solution was chosen

This page is more than a gallery. Each project is documented through challenge, solution, result, technology choices and a link to details.

Challenge
Solution
Result
Technology and demo

How to read them

What each story shows

Projects

Challenge

We start with a real business or technical constraint: speed, reliability, vendor dependency or manual work.

Projects

Solution

We show the architecture direction, key integrations and why specific technologies were chosen.

Projects

Result

We record practical value: saved time, clearer operations, faster workflow or better operational control.

Project atlas

See where the same architecture principles repeat

The catalog is not a screenshot gallery. It is a map of systems: content platforms, AI operations, internal tools, infrastructure and marketplace products have different risks, but many reusable technical decisions.

33

Dev-story pages

50

Technology signals

33

Detailed articles

51

Module zones

our projects

Projects are documented as dev-story breakdowns: the problem, architecture, demo plan, technology choices, lessons and related articles in one place.

WebEdge public site screenshotDev-story
AstroTypeScriptTailwind

WebEdge public site

Article 06 sections 03 modules

A fast multilingual site connecting services, content and the project catalog.

Challenge
WebEdge needed one place for services, stack, content and work examples without shipping unnecessary JavaScript.
What we did
We built an Astro-generated site with shared design tokens, localized content and fast static pages.
Result
The team has a clear public showcase that can expand without introducing another platform.
Read dev-story
Vue 3ConvexAgent runners

AI agent control plane

Article 06 sections 04 modules

An internal workspace for agent jobs, instructions and run status.

Challenge
Agent experiments become hard to track when prompts, runs and outputs live in separate places.
What we did
We created a control layer where tasks, agent context and run status sit in one real-time interface.
Result
The team can see what is running, what needs review and which agent workflows are reusable.
Read dev-story
RustTypeScriptConvex

Self-hosted reactive database platform

Article 06 sections 04 modules

An experimental data layer for real-time apps and infrastructure control.

Challenge
Some systems needed more operational control than fully managed services provide.
What we did
We built a reactive data platform module with a Rust core and TypeScript integrations.
Result
The team can test self-hosted synchronization, observability and deployment scenarios.
Read dev-story
Vue 3ConvexScheduling

Calendar booking platform

Article 06 sections 04 modules

Time booking, team schedules and notifications in one interface.

Challenge
Bookings require fast visibility between customers, administrators and service providers.
What we did
We built a scheduling platform with live calendars, availability windows and notification integrations.
Result
The booking workflow is clearer and teams coordinate less manually.
Read dev-story
Node.jsPostfixDKIM

Mail infrastructure

Article 06 sections 04 modules

Transactional email, sending modules and delivery control in a managed environment.

Challenge
Products needed reliable email without every project solving delivery separately.
What we did
We grouped mail server, sending API and a simple Resend-style module into one infrastructure set.
Result
Applications can use a shared email layer while delivery settings are managed centrally.
Read dev-story
TypeScriptBank integrationsCrypto

Payment core

Article 06 sections 04 modules

A shared payment integration base for products that need multiple payment paths.

Challenge
Payment integrations repeated across products and needed consistent states and error models.
What we did
We separated payment logic into a core with adapters for banking and alternative channels.
Result
New products can connect payments through a shared model and maintain operations more simply.
Read dev-story
JavaScriptVueEdge delivery

CDN and media delivery

Article 06 sections 04 modules

A file and media layer for faster delivery and management.

Challenge
Media files across products need to load quickly and be managed consistently.
What we did
We built a CDN management module with an admin interface and edge delivery logic.
Result
File paths, access and delivery can be maintained in one infrastructure layer.
Read dev-story
Vue 3ConvexTracking

Short links and designer QR

Article 06 sections 04 modules

Campaign links, QR codes and click tracking in one tool group.

Challenge
Marketing and operations flows need short links, QR codes and clear usage visibility.
What we did
We combined short-link and QR generation modules with Convex data and tracking events.
Result
The team can create public redirects and see usage without a separate third-party tool.
Read dev-story
SwiftWhisperNode.js

Voice, transcription and downloader tools

Article 06 sections 04 modules

A tool group for media input, speech recognition and file preparation.

Challenge
Voice and media prototypes need recordings, text and sources prepared quickly for later processing.
What we did
We built separate voice, transcription and downloader modules that can connect into workflows.
Result
Speech input and media-processing experiments move faster because the base tools are ready.
Read dev-story
Vue 3ConvexSwiftKotlinWearables

Fitness ecosystem

Article 06 sections 05 modules

A set of coach, client, mobile and wearable integration modules.

Challenge
A fitness product spans many surfaces: web UI, coach tools, mobile apps and device data.
What we did
We grouped the ecosystem into the core platform, coach apps and separate Apple Watch, Android and wearable adapters.
Result
Each module can evolve separately while keeping one real-time data and user-experience direction.
Read dev-story
PythonVueLocal AI

Local food AI prototype

Article 06 sections 04 modules

An experiment with food data, a local model and recommendation flow.

Challenge
Food recommendations need fast experimentation without sending every data point to external services.
What we did
We built a Python and Vue prototype for testing local AI scenarios with structured data.
Result
Ideas can be validated with lower risk before committing to a broader product architecture.
Read dev-story
Vue 3ConvexCMS sync

ePokalbis community forum

Article 06 sections 04 modules

A public space for community conversations, topics and open discussion.

Challenge
The community needed a clear place to start topics, continue conversations and find relevant discussions.
What we did
We organized the public forum structure, topic flows and content pages so communication stays in one place.
Result
Visitors can read topics, join discussions and return to community conversations without switching channels.
Read dev-story
Vue 3ConvexScraping

Real estate marketplace and radar

Article 06 sections 04 modules

A real estate listing interface and monitoring module for market signals.

Challenge
Real estate needs not only listings, but also signals about source and listing-status changes.
What we did
We connected the housemarket interface with a separate data collection and monitoring module.
Result
The listing experience and market radar can grow together while staying separately maintainable.
Read dev-story
Vue 3ConvexMarketplace

Service marketplace

Article 06 sections 04 modules

A prototype for service providers, enquiries and categories.

Challenge
A services market needs to connect categories, providers and enquiries without a heavy start.
What we did
We built a marketplace structure with categories, profile logic and an enquiry path.
Result
The project can test service niches and expand features based on real usage.
Read dev-story
Vue 3ConvexListings

Universal classifieds marketplace

Article 06 sections 04 modules

A listings structure for items, categories and local discovery.

Challenge
General classifieds need a flexible model that is not locked to one product category.
What we did
We built a listings, categories and browsing foundation on a Convex data layer.
Result
The platform can adapt to different classifieds verticals without starting from scratch.
Read dev-story
Vue 3TypeScriptStatic site

Vilniaus Verinelis site

Article 06 sections 04 modules

An easy-to-maintain informational site for community and parents.

Challenge
The informational site needed fast loading, clear structure and simple content presentation.
What we did
We built a static site on Vue and TypeScript with organized page architecture.
Result
Information is easier to present and the site remains simple to maintain.
Read dev-story
NuxtCMS importStatic generation

Lazdynelis kindergarten CMS/static demo

Article 06 sections 04 modules

A content import and static generation experiment for a kindergarten-style site.

Challenge
Education sites need simple content updates and fast public delivery.
What we did
We built a Nuxt demo with a CMS import flow and static page generation approach.
Result
The team can evaluate how content moves from administration into a fast public site.
Read dev-story
Vue 3ConvexRealtime game state

Private poker room app

Article 06 sections 04 modules

Real-time room state, actions and game prototype logic.

Challenge
A game prototype needs synchronized state so several participants see the same table.
What we did
We built a real-time room model with actions, player state and interface updates.
Result
The prototype can test game mechanics and synchronization limits in a controlled environment.
Read dev-story
TypeScriptVue QueryConvex

Convex Vue Query adapter

Article 06 sections 04 modules

A library-style module connecting Convex data with Vue Query workflows.

Challenge
Vue projects needed a smoother way to use Convex queries alongside familiar data-fetching patterns.
What we did
We built a TypeScript adapter that defines the bridge between Convex and Vue Query usage.
Result
Components can use a more consistent data model and repeat less integration code.
Read dev-story
TypeScriptTelegramLLM gateways

OpenClaw mini gateway

Article 06 sections 04 modules

A lightweight LLM and messaging gateway prototype for experiments.

Challenge
Experiments with chat channels and LLMs need a small, easy-to-change middle layer.
What we did
We built a TypeScript mini gateway for connecting Telegram-style channels and model calls.
Result
New agentic or chat scenarios can be tested before moving them into a larger platform.
Read dev-story
SkillsAgent workflowsDocumentation

Agent skills library

Article 06 sections 04 modules

Reusable workflow descriptions that help agents operate consistently.

Challenge
Agent quality depends on clear instructions, but those often remain inside chats or scattered files.
What we did
We built a skills library with documented workflows, rules and usage context.
Result
Repeatable work can run more consistently and new agent flows are documented faster.
Read dev-story

FAQ

How project decisions are made

Why do some projects not have a video yet?

Some demos are still being prepared or cannot show client data. In those cases we share the technical story without sensitive information.

Can you show more detail on a call?

Yes. During a consultation we can show a closer architecture level when it does not violate client confidentiality.

Can a project like this be adapted to another industry?

Usually yes. We separate reusable architecture from client-specific business logic first.

Have a similar challenge?

Send a short description of the situation. We will suggest whether to start with a prototype, integration or broader system.

Discuss a project