konto-deploy
Deploy and run Konto (personal finance dashboard) locally. Use when setting up a new Konto instance, troubleshooting installation, or helping users get started with Konto.
Best use case
konto-deploy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy and run Konto (personal finance dashboard) locally. Use when setting up a new Konto instance, troubleshooting installation, or helping users get started with Konto.
Teams using konto-deploy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/konto-deploy/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How konto-deploy Compares
| Feature / Agent | konto-deploy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deploy and run Konto (personal finance dashboard) locally. Use when setting up a new Konto instance, troubleshooting installation, or helping users get started with Konto.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Konto — Local Deployment Personal & professional finance dashboard. Bank sync, crypto, investments, budget, tax tools. ## Prerequisites - Node.js 18+ and npm 9+ - `openssl` (for encryption key generation) ## Installation (3 commands) ```bash git clone https://github.com/angelstreet/konto.git cd konto npm install ``` ## Configuration ```bash # Create env from template cp .env.example backend/.env # Generate and set encryption key KEY=$(openssl rand -hex 32) sed -i "s/^DB_ENCRYPTION_KEY=$/DB_ENCRYPTION_KEY=$KEY/" backend/.env ``` ### Minimal config (works immediately) Only `DB_ENCRYPTION_KEY` is required. Everything else is optional. ### Optional integrations | Feature | Env vars | Sign up | |---------|----------|---------| | Bank sync | `POWENS_CLIENT_ID`, `POWENS_CLIENT_SECRET`, `POWENS_DOMAIN` | [powens.com](https://powens.com) | | Production auth | `CLERK_SECRET_KEY`, `VITE_CLERK_PUBLISHABLE_KEY` | [clerk.com](https://clerk.com) | | Coinbase | `COINBASE_CLIENT_ID`, `COINBASE_CLIENT_SECRET` | [developers.coinbase.com](https://developers.coinbase.com) | | Google Drive | `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET` | [console.cloud.google.com](https://console.cloud.google.com) | ## Running ```bash # Start both frontend + backend npm run dev ``` - Frontend: http://localhost:3004/konto/ - Backend API: http://localhost:5004/api/ - Login: `user` / `user` (local dev, no Clerk needed) ## Sandbox / Demo Mode Konto auto-seeds demo data for the default user: - Bank accounts (checking, savings, investment) - Crypto wallets (BTC, ETH, XRP) - Investment positions (PEA, Assurance Vie, PER) - 14 months of transaction history - Real estate and vehicle assets Just log in and explore — no external API keys needed. ## Building for Production ```bash npm run build # Frontend: serve frontend/dist/ as static files # Backend: node backend/dist/index.js ``` ### Vercel deployment ```bash cd frontend && vercel cd backend && vercel ``` ## Ports | Service | Port | URL | |---------|------|-----| | Frontend (dev) | 3004 | http://localhost:3004/konto/ | | Backend API | 5004 | http://localhost:5004/api/ | ## Troubleshooting | Problem | Solution | |---------|----------| | `ENCRYPTION_KEY` error | Run `openssl rand -hex 32` and set in `backend/.env` | | Port 3004 in use | `lsof -i :3004` to find process, kill or change `VITE_DEV_PORT` | | Port 5004 in use | Change `PORT` in `backend/.env` | | Clerk errors locally | Leave `CLERK_SECRET_KEY` empty — local dev bypasses Clerk | | Empty dashboard | Log in as `user/user` — demo data seeds on first backend start | | Bank sync not working | Requires Powens API keys (optional for demo) | ## Tech Stack | Layer | Tech | |-------|------| | Frontend | React 18 + TypeScript + Vite + Tailwind CSS + Recharts | | Backend | Hono + TypeScript + Node.js | | Database | SQLite (local) or Turso (cloud) | | Auth | Clerk (optional) | ## API Endpoints (key ones) | Endpoint | Description | |----------|-------------| | `GET /api/bank/accounts` | Bank accounts | | `GET /api/investments` | Investment positions | | `GET /api/transactions` | Transaction history | | `GET /api/companies` | Companies (pro) | | `GET /api/patrimoine/summary` | Net worth summary | | `GET /api/preferences` | User preferences | Full API docs: `docs/API.md` in the repo.
Related Skills
NestJS Deployment
Docker builds, Memory tuning, and Graceful shutdown.
Multi-Platform Deployment
This skill should be used when the user asks to "deploy application", "deploy to production", "release app", "deploy to AWS", "deploy to Vercel", "deploy to Kubernetes", "iOS deployment", "Android deployment", "deploy smart contract", "web3 deployment", "deploy to multiple platforms", or needs guidance on deployment strategies across web, mobile, and blockchain platforms.
managing-astro-deployments
Manage Astronomer production deployments with Astro CLI. Use when the user wants to authenticate, switch workspaces, create/update/delete deployments, or deploy code to production.
kubernetes-deployment
Deploy, manage, and scale applications on Kubernetes clusters using manifests, Helm charts, and autoscaling configurations.
kubernetes-deployer
Package and deploy applications to Kubernetes with Dockerfiles, Helm charts, and local Minikube deployment. Use when containerizing applications, creating Kubernetes manifests, setting up Helm charts, deploying to Minikube, or preparing cloud-ready configurations. Focuses on local-first deployment with stateless services.
kamal-deploy
Expert-level Kamal deployment guidance for deploying containerized applications to any server. Use this skill when users ask about Kamal, container deployment, zero-downtime deployments, deploying Rails/web apps to VPS/cloud servers, kamal setup, kamal deploy, Docker deployment without Kubernetes, or deploying to Hetzner/DigitalOcean/AWS with Kamal. Also use when users mention DHH's deployment tool, 37signals deployment, or want an alternative to Heroku/Render/Vercel with self-hosted infrastructure.
kagenti:deploy
Deploy or redeploy the Kagenti Kind cluster using the Python installer - quick redeploy, manual steps, and troubleshooting
k8s-simple-deploy
Assists with deploying simple apps to Kubernetes consisting of a deployment and a service.
k8s-deploy-auto
Kubernetes deployment automation workflows for CI/CD pipelines, GitOps, and scripted deployments. Use when automating k8s deployments, creating deployment scripts, integrating with GitHub Actions/GitLab CI, implementing rollout strategies, or setting up ArgoCD/Flux workflows.
gke-deployment
Deploy, configure, and manage Kubernetes workloads on GKE with Deployments, Services, Ingress, HPA, health probes, ConfigMaps, and Secrets. Use when deploying containers to GKE, configuring load balancers, setting up autoscaling, writing health checks, managing environment configs, or troubleshooting pod issues.
frontend-deployment
Deploy frontend applications from aramb.toml. Creates frontend service, resolves backend references from deployment outputs, builds static files, and deploys with environment variables. Returns deployment URL. Use for all frontend deployments.
featbit-deployment-kubernetes
Deploys FeatBit to Kubernetes using Helm Charts. Use when user mentions "Kubernetes", "Helm", "K8s", "kubectl", works with values.yaml files, asks about "cloud deployment", "AKS", "EKS", "GKE", "ingress", or needs production-grade container orchestration setup.