Taskline
Complete team project management for the teams Trello and Asana priced out — board, list and calendar over one task model, at one flat price.
Taskline is team project management: projects that hold task boards, with the same tasks viewable as a board, a list or a calendar. It is aimed at small and mid-sized teams that want the complete feature set at one flat price per workspace rather than per seat.
The same work reads correctly to the person who plans and the person who executes.
Teams rarely disagree about what needs doing. They disagree about how to look at it. The person running the week wants dates; the person doing the work wants a queue; the one reporting upward wants stages. When a tool picks one of those, the other two rebuild it somewhere else — a spreadsheet, a personal list, a recurring meeting whose only purpose is translation. That copy drifts within days, and then the question stops being what is late and becomes which version is right. The cost is not the tool; it is the hour a week each person spends maintaining their own translation of it.
- Board / list / calendar views
- Projects + kanban board (drag-drop)
- Rich tasks (assignees, due dates, checklist, labels, priority, attachments)
A client sees their project and nothing else, without a second tool.
Most work involves someone who is not on the payroll — a client, a contractor, an agency. The usual options are both bad. Invite them properly and they can read every other project, including the ones about them. Keep them out and the work moves to email attachments and screenshots, where nobody can tell which version is current and decisions stop being recorded anywhere. Teams end up running a second, informal project tool for outsiders, and the two disagree by the end of the first week. What it costs is the thing everyone notices last: the project history has a hole in it exactly where the customer was.
- Guest role (project-scoped)
Adding the person who only comments twice a month costs nothing.
Per-seat pricing quietly changes who gets to participate. The finance lead who needs to see two projects, the designer who joins for a sprint, the founder who checks in on Fridays — each one is a line item, so somebody decides they can make do with a forwarded screenshot instead. The work of that decision does not disappear; it moves into direct messages and meetings, out of the record. Six months later the project history shows only the people who were cheap enough to include, and the reason anything was decided lives in someone memory. Flat pricing removes the conversation entirely.
- Project setup templates (working instantiation)
- Team dashboard
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Pabbly Connect
Freshsales
Pipedrive
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 54 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 68 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · board_columns · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · labels · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · project_members · project_templates · projects · provider_prices · push_devices · report_templates · roles · scheduled_tasks · seo_meta · subscriptions · task_activity · task_assignees · task_attachments · task_comments · task_labels · task_mentions · task_reminder_log · tasks · theme_page_sections · theme_section_library · theme_sections · translations · user_project_prefs · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 2 required.
The chassis. Next 16 on any Node host, with Postgres, auth, storage and the realtime channel the boards use coming from Supabase.
Three scheduled jobs ship declared for Vercel. On any other host they are a cron configuration you wire by hand — not a service you procure, but reminders only go out once something calls them.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 144,036 lines across the application and its database, 68 tables defined by 101 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Taskline demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 4 of them: Team collaborator, Guest collaborator, Workspace owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 73 page modules and 286 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A scheduled runner for due-date reminders. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 101 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $199?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.