Everything you need to own and operate the Kolamba platform — February 2026
| Service | Transfer Method | What You Get | Monthly Cost |
|---|---|---|---|
| GitHub Repository | Repository transfer | Full source code, commit history, CI/CD workflows | Free |
| Vercel Project | Project transfer | Frontend hosting, auto-deploy on git push, environment variables | Free (Hobby) / $20 (Pro) |
| Railway Project | Project transfer | Backend API server, PostgreSQL database with all data | ~$5–15 (usage-based) |
| Cloudinary Account | Credential handover | Image/media hosting, all uploaded files | Free (25GB) / $89 (Plus) |
| Google Cloud Project | Owner role transfer | OAuth login credentials for Google Sign-In | Free |
| Domain | Registrar transfer | kolamba.com / kolamba.org domain ownership | ~$12/year |
Create accounts on these platforms before the transfer call. All have free tiers.
SECRET_KEY and any API keys you wish to rotate.
Update them in Railway and Vercel environment variables. This ensures only you have access.
| What | URL | Notes |
|---|---|---|
| Live Website | kolamba.vercel.app | Frontend — auto-deploys when you push to GitHub |
| Backend API | kolamba-api-production.up.railway.app/api | REST API — auto-deploys from GitHub |
| API Documentation | .../api/docs | Interactive Swagger docs for all endpoints |
| Health Check | .../api/health | Returns {"status":"healthy"} when backend is running |
| GitHub Repo | github.com/luvchikavi/kolamba | Will change to your username after transfer |
| Railway Dashboard | railway.app/dashboard | Backend server + database management |
| Vercel Dashboard | vercel.com/dashboard | Frontend deployment management |
| Cloudinary Dashboard | console.cloudinary.com | View and manage uploaded images |
Both the frontend and backend deploy automatically when code is pushed to the main branch on GitHub.
You don't need to run any commands — just push your code.
Database schema changes are handled by Alembic (Python migration tool).
Migrations run automatically on each Railway deployment via start.sh.
No manual database management is needed.
| Task | How To |
|---|---|
| View server logs | Railway dashboard → kolamba project → Backend service → Logs tab |
| View deployment history | Vercel dashboard → kolamba → Deployments tab |
| Access database | Railway dashboard → PostgreSQL service → Data tab (or use connection string with pgAdmin) |
| Update environment variables | Railway: Service → Variables tab. Vercel: Project → Settings → Environment Variables |
| Rollback a deployment | Vercel: Deployments → click previous deployment → Promote to Production |
| Add a custom domain | Vercel: Settings → Domains → Add → follow DNS instructions |
| Approve pending artists | Login as admin → Admin Dashboard → Artists → change status to "active" |
Reference: Proposal PP-KOL-002-26 v2.0 — 40 hours over 4 weeks, 7 MVP phases + post-MVP roadmap.
| Phase | Planned (h) | Status | Notes |
|---|---|---|---|
| Phase 1: Foundation & Design | 6h | ✓ Complete | Git repo, CI/CD, DB schema, Alembic migrations, wireframes |
| Phase 2: Homepage & Search | 8h | ✓ Complete | Hero section, search endpoint with filters, category navigation |
| Phase 3: Artist Profiles | 6h | ✓ Complete | Artist CRUD, listing grid, full detail page |
| Phase 4: Community & Booking | 6h | ✓ Complete | Community CRUD with geolocation, booking flow with status tracking |
| Phase 5: Tour Logic | 8h | ✓ Complete | Haversine clustering, multi-factor scoring, community size weighting. No map view. |
| Phase 6: Auth & Dashboard | 4h | ✓ Complete | JWT auth with refresh tokens, role-based dashboards (artist, community, admin, agent) |
| Phase 7: QA & Deployment | 2h | ✓ Complete | Deployed to Vercel + Railway production |
| Phase 9: Smart Tour Algorithm | 4h | ✓ Complete | Post-MVP. Multi-factor scoring: bookings 25%, audience 25%, budget 20%, route 15%, dates 15% |
| Feature (from Proposal) | Status | Actual Delivery |
|---|---|---|
| Homepage & Search | ||
| Hero section with Kolamba vision | ✓ Done | Dark gradient hero, bilingual tagline, kolamba.org logo |
| Featured artists display | ✓ Done | Featured artists carousel on homepage |
| Category navigation | ✓ Done | Category chips, /categories/[slug] pages |
| Search with filters | ✓ Done | Full search page with category, price, and language filters |
| Responsive on mobile | ✓ Done | Tailwind responsive breakpoints throughout |
| Artist Features | ||
| Artist listing grid | ✓ Done | /artists page with filterable card grid |
| Artist detail profile page | ✓ Done | /artists/[id] with full bio, categories, pricing, booking CTA |
| Artist registration | ✓ Done | /register/artist with comprehensive form, backend approval flow |
| Artist profile editing | ✓ Done | Artist dashboard → Settings (name, bio, pricing, categories, contacts) |
| Artist approval workflow | ✓ Done | Status: pending → active/rejected. Admin panel for approval. |
| Community Features | ||
| Community registration | ✓ Done | /register/community with location, audience size, event types |
| Community profile (location, audience) | ✓ Done | Full profile with geolocation, size, event types, settings page |
| Community dashboard | ✓ Done | Events, quotes, messages, settings, nearby touring artists |
| Discover artists from dashboard | ✓ Done | Interest-based matching, price/distance/category filters, inline cards (added Feb 2026) |
| Booking | ||
| Booking request submission | ✓ Done | Booking form on artist profile page, full CRUD API |
| Booking status tracking | ✓ Done | Status workflow: pending → approved/rejected/cancelled |
| Email notifications for bookings | ● Partial | Resend SDK configured, sending logic not active |
| Tour Logic | ||
| Proximity-based tour suggestions | ✓ Done | Haversine distance + BFS clustering algorithm |
| Community size in ranking | ✓ Done | 25% weight in multi-factor tour scoring (Phase 9) |
| Valid tour route generation | ✓ Done | Nearest-neighbor routing with tour date management |
| Authentication & Dashboards | ||
| JWT login / register | ✓ Done | JWT with access + refresh tokens, secure cookie flow |
| Google OAuth sign-in | ● Partial | Backend endpoint complete, frontend button not wired |
| Role-based dashboards | ✓ Done | 4 dashboards: Artist, Community, Admin, Agent |
| Admin panel | ✓ Done | Artist approval, user management |
| Technical Requirements | ||
| Site loads in < 3 seconds | ✓ Done | Next.js SSR, Vercel edge network |
| Cross-browser (Chrome, Safari, Firefox) | ✓ Done | Standard React/Tailwind — works in all modern browsers |
| SSL certificate | ✓ Done | Auto-provisioned by Vercel and Railway |
| Production deployment | ✓ Done | Vercel (frontend) + Railway (backend + DB), auto-deploy on push |
| Bonus Feature | Description |
|---|---|
| Refresh token mechanism | Secure token refresh for persistent login sessions |
| Agent dashboard | Fourth role type (agent) with dedicated dashboard |
| Messaging system | In-app messaging for artists and communities |
| Smart tour algorithm (Phase 9) | Multi-factor scoring: bookings, audience, budget, route efficiency, date clustering |
| Discover artists (dashboard) | Interest-based artist matching with filters on community dashboard |
| Docker production configs | Full containerization for backend deployment |
| Comprehensive documentation | Architecture docs, API docs (Swagger), brand guidelines, this handoff guide |
| Address autocomplete | Geocoding component for community registration |
| Full design transformation | Complete UI redesign from the original kolamba.org — modern dark-gradient hero, bilingual layout, responsive card grids, branded dashboard experience |
| Artist tour management | Dedicated tour management section in artist dashboard — create, edit, and track tour dates with location and scheduling |
| Quote request system | Communities can request and manage quotes from artists, with full workflow tracking on the community dashboard |
Drishti Consulting provides 30 days of post-handoff support at no additional charge. This includes assistance with the transfer process, troubleshooting, and answering questions about the platform architecture. For ongoing maintenance or new feature development, please contact us to discuss a support arrangement.