Ontra unites the command center, tasks, project plan, sprints, goals, documents, reports, and support tickets in one workspace. List, board, and map show the same record. Scale with roles, companies, and API access without breaking the team's pace.
The way teams prefer to work
Why Ontra
Task, plan, document, and report read from the same record. Permissions are precise; growth is not a new account. Four decisions carry the team's every day.
Work you open in the list moves on the board, pins on the map, enters sprint scope, and links to a document. Assignee, status, tags, and permissions stay the same record everywhere — no copies, no drift.
Task · Project · Plan · Document
Access at project, folder, and list level — not just by role. The menu simplifies to match permissions; guests only see, admins configure every resource. Everyone sees their work, nothing more.
Role · Project · Folder · List
The command center shows SLA, overdue, unassigned, and aging work at once. Effort, close speed, repeat, and delay reports say who is overloaded and which work is how many days late — without a sentence.
Dashboard · Report · SLA
Holdings and branches grow in one account without mixing data. A new company is not a new login; ready permission templates and scoped API keys mean scaling is not rebuilding.
Holding · Branch · API
Platform
Ontra isn't a task list — it's the operating system where work is planned, executed, documented, and measured. Eight surfaces, one record.
Single record
Same data, eight surfaces.
Open a task in the list, move it on the board, pin it on the map, add it to sprint scope, attach it to the plan — assignee, status, tags, and permissions stay intact everywhere. Reports and support tickets read from the same workspace.
01Command centerOpen work, SLA, overdue items, team capacity, and workspace health at a glance. Export to Excel or PDF.KPISLAAging workExport
05Sprints & goalsSprint scope, velocity, and completion rate side by side. Goals bind to milestones and key results.ScopeVelocityGoalKR
02TasksList, board, and map show the same record. Folders, lists, tags, saved views, and shortcuts keep the pace.ListBoardMapSaved view
06DocumentsDecisions live inside the project. A page links to a task; a share link can take a password and an expiry.Page treeTask linkShare
03ProjectsOwner, category, effort budget, and progress on one screen. From a project you move into the plan, documents, and sprints.OwnerCategoryProgress07ReportsEffort, repeat, close speed, delay, and activity. Who is overloaded, which work is how many days late — without a sentence.EffortDelaySpeedActivity
04Project planModule, use case, feature, and milestone bind in one tree. What will be delivered is read, not debated.ModuleUse caseFeatureMilestone
08Support & learningCustomer tickets stay in a queue. The in-panel help center walks through shortcuts, views, and setup step by step.TicketGuideShortcutFeatures
Six layers, one record. Keep scrolling — each layer describes a surface that actually runs in the panel, not a slogan.
Scroll ↓
Switch views without moving the data. Work can be a task, bug, feature, or idea. Filter by status, priority, folder, list, tag, milestone, and assignee; save the view and make it default. N for a new item, Ctrl+K for the palette, ? for shortcuts. Bulk edit and import keep the pace.
The plan binds four kinds: a module draws scope, a use case carries the scenario, a feature names the concrete work, a milestone locks the delivery. Tasks attach to this tree; sprint scope does not drift from the plan. Goals sit on milestones and key results — the quarter is read, not debated.
The page tree belongs to the project. It links to a task, is searchable, and multiplies from a template. When you share outside, put a password and an expiry on the link; the lock screen says who can see it. New hires find the decision on the page on day one, without asking someone.
The command center reads open work, SLA, critical blockers, and team utilization at once. Effort shows who spent how many hours, delay how many days a due date slipped, close speed the time from open to close, repeat how often the same work lands on the same person, activity who did what. Export to Excel or PDF.
Admin, project lead, member, and guest — the interface simplifies to match permissions. Access is not only by role; it cuts at project, folder, and list level. Custom task statuses and project categories belong to the workspace. An invited person enters the right door and never sees the wrong record.
Multiple companies sit in one panel. Scoped API keys connect task and project flows to your own systems; the key is shown once, then hidden. Customer tickets walk a queue. The in-panel help center walks through setup, shortcuts, and views — without leaving for another tab.
Inside the panel
Help center and support tickets are open.
Setup guides, shortcuts, and the customer queue live in the same workspace. Don't switch tools to learn.
Modules
Twelve surfaces, one data model — no extra modules, no extra subscriptions. All of them open on the same plan.
%86completion01TasksList, board, and map show the same record. Filter by folder, list, tag, type (task / bug / feature / idea), and saved view; N, Ctrl+K, and ? keep the pace.02ProjectsOwner, category, effort budget, open work, and SLA in one table. From project detail you move into the plan, documents, and sprints on the same spine.03Project planA module draws scope, a use case carries the scenario, a feature names the concrete work, a milestone locks delivery. Tasks attach to this tree.
04SprintsScope, date range, completion rate, and velocity side by side. An emergency sprint opens from the current queue; board and list read the same sprint.05GoalsA goal sits on a milestone; a key result counts progress. Health and status stay visible; sprint delivery does not detach from the goal.
06DocumentsThe page tree belongs to the project and links to a task. When you share outside, put a password and an expiry on the link; the decision does not vanish in chat.07ReportsEffort, repeat, close speed, delay, and activity. The command center gathers SLA, aging work, and team utilization in one glance; export to Excel or PDF.08Support ticketsThe customer queue walks open, waiting for reply, in progress, and resolved. N for a new ticket; search and status chips keep a personal queue from scattering.
09Command centerOpen work, critical blockers, sprint health, and team capacity on one screen. Period filter, quick search, and industry examples complete the first look of the day.
10Folders & listsClient, product, or team breakdown lives in a folder. A list belongs to a folder, a task to a list; permissions cut at folder level.11Team & rolesAdmin, project lead, member, guest. Custom task statuses and project categories belong to the workspace. An invited person enters the right door.12API & billingA scoped key is copied once, then hidden. Subscription, seats, and payment sit in the same tenant settings. Growth is not opening a new account.All twelve on one plan. Same record, same permissions, no extra invoice.
Try the modulesOntra isn't a setup wizard — it's a rhythm that runs every day of the week. Four verbs, with the panel's real surfaces, become the team's shared reflex.
Bring everything scattered through one door.
Excel, chat, email, boards… Translate them all into one language: work, owner, date, project. With import and bulk add, by end of day one no work is stuck "with someone." Folders and lists carry the client or product breakdown from that day.
Every task has an owner and a date.
Work without an owner or date is just a wish. In Ontra every card is a promise: who does it, when it ends, which project and which milestone it belongs to. Priority, tags, and a saved view prepare the same filter every morning. The unassigned queue stays visible on the command center.
Let the week flow; blockers reveal themselves.
Board, sprint, and project plan draw from the same source. Stuck work is not invisible; the delay report says how many days late, effort who is full, activity who did what. The document keeps the decision next to the work — sprint close is a rate you read, not a guess.
Grow the team without shaking the system.
New branch, new client, new team… Ready permission templates, multi-company, and scoped API mean scaling is not rebuilding. Support tickets walk a queue; the help center onboards the new hire into the panel. Goals and reports close the month's account without a meeting.
7 days free. Take the first step of the rhythm today — no credit card required.
Start building your rhythmSolutions
Software, agency, holding, or operations — the structure is yours; Ontra adapts with the panel's real surfaces.
Tasks, bugs, and features sit in the same queue. Sprint scope does not drift from features and milestones in the project plan; completion rate is a number you read on the panel, not a guess.
Plan → Task → Sprint → Report
Every client is a separate folder, every delivery a separate project — operations stay in one panel. Approval lives in the document; the team only sees the relevant client.
Client → Folder → Delivery → Approval
Holding, branches, and teams under one roof. Data does not mix; permissions cut at the resource. The admin panel sees the full structure; a branch sees its own work.
Company → Branch → Role → Report
Field, store, or support queues carry the same work on the map and in the list. Overdue, unassigned, and repeating work stays visible in reports.
Ticket → Task → Map → Report
At your fingertips. Work you start on desktop continues on your phone — same data, same permissions, same speed.
Mobile experience
No app store wait. Open the link, sign in — projects, sprints, and documents at your fingertips.
Milestones, tasks, and documents in the same context — goodbye to scattered tools.
Kanban · List · Sprint
Statuses, sprints, and roadmap update instantly; the team stays in sync.
Live sync · PWA
Rich editor, page structure, and project links keep knowledge from getting lost.
Editor · Page tree
Secure scaling with roles, permissions, and multi-company support.
RBAC · Multi-company
Your data doesn't scatter across dozens of external plugins. Ontra quietly draws your company's digital boundaries with a resource-based hierarchical architecture.
Data doesn't scatter — it's sealed in one secure core.
Data is encrypted to banking standards both at rest and in transit.
Each company's and workspace's data is absolutely isolated from other organizations.
Daily snapshots and zero data-loss assurance against disaster scenarios.
“Security isn't a layer added later; it's the foundation of Ontra's architecture.”
Your data doesn't scatter across five micro-plugins or third-party storage services. Tasks, documents, and roadmaps live on one sealed backbone.
Permission isn't just a restriction tool — it creates mental clarity by hiding menus and buttons that distract employees.
Who accessed what data and when is never a question. Every action is recorded with an immutable timestamp that safeguards institutional trust.
Pricing
One plan, all features included. Pay per seat — add as you grow, remove as you shrink.
One plan · Everything included
Billed upfront on annual payment.
Team size
Save $180 vs monthly
No credit card · Cancel anytime
Everything included
50+ seats?
Let's talk volume licensing and onboarding support for enterprise teams. Get a quote →
Customer stories
Teams who left scattered tools behind for one calm panel tell their story.
“After switching to Ontra, we stopped having meetings just to ask about project status. Everything is in the panel — clear.”
“The roadmap gave the team a shared language. Priorities aren't debated anymore — they're read.”
“When documents live inside projects, knowledge loss ended. New hires are productive from day one.”
We're here to help.
For software teams, agencies, holdings, and field/operations teams that run projects. The shared need is the same: task, plan, document, and report stay on one record; permissions cut at project, folder, and list level.
Command center; tasks (list, board, map, saved views, tags, folders, lists, shortcuts); projects and the project plan (module, use case, feature, milestone); sprints and goals; documents (page tree, task link, password-protected share); reports (effort, repeat, close speed, delay, activity); support tickets; help center; team, roles, custom task statuses, project categories, multi-company, and scoped API keys. All on one plan, no extra packs.
Three layouts: list, board, map. Work type can be task, bug, feature, or idea. Filter by status, priority, project, folder, list, tag, milestone, and assignee; save the view and make it default. N for a new item, Ctrl+K for the command palette, ? for the shortcut window. Bulk edit and import keep the pace.
The plan is the project's spine, not a timeline slide. A module draws scope, a use case carries the scenario, a feature names the concrete work, a milestone locks delivery. Tasks attach to this tree. Goals sit on milestones and key results; sprint scope is read from the plan.
Effort: who closed how many tasks and their load. Repeat: how often the same work lands on the same person. Close speed: time from open to close. Delay: how many days or hours a due date slipped. Activity: who opened, closed, or commented. The command center reads these with SLA, aging work, and team capacity; export to Excel or PDF.
Yes. The page belongs to the project and links to a task. You put a password and an expiry on the share link; the lock screen says who can see it. The decision does not vanish in chat.
You complete the move step by step with task import, bulk edit, and folder/list breakdown. The in-panel help center covers first login, shortcuts, and views. We also offer onboarding support if you'd like.
There are admin, project lead, member, and guest roles. Alongside that, access is defined at project, folder, and list level. The menu simplifies to match permissions; guests only see, admins configure the resource.
You generate a scoped API key in tenant settings. The full text is shown once; after a refresh it is hidden. Connect task and project flows to your own systems. There is no webhook yet; key revoke and rotation happen from the panel.
Yes. All surfaces are open for 7 days without a credit card. Cancel anytime; pay monthly or yearly per seat.
The web app runs as a full panel in mobile browsers and can be added to the home screen as a PWA. Native store apps are on the roadmap.
Your data is stored encrypted at rest and in transit on secure cloud infrastructure. Tenants are isolated from each other. Role-based access, session management, and an audit trail are on by default.
Resources
The blog explains why work stays on one record: access, sprints, the demo, and per-seat pricing.
ProductWhen tasks and docs share one record, work stops scatteringList, board, and roadmap are views of the same record. A decision is made once and every surface shows the same truth. This piece explains how a pile of tools delays delivery and how Ontra binds one record.
SecurityFine-grained access lets the team breatheNot everyone needs every project. Add project, folder, and list access on top of roles, and privacy becomes the default. In agencies and holdings the leak is rarely malice — it is the oversized shortcut “admins see everything.”
SetupFinish the workspace in the 7-day demo, not the tool tourNo credit card. When the demo ends the app locks and data stays. Load real work in week one instead of touring screens: a project, roles, the live sprint, the docs tree, and the first report. A showroom tour does not pick a tool; a sitting record does.
DeliveryIf the sprint date slips, the problem is visibility, not speedLate work piles up without a report. When due date, delay, and comments live on the same task, stand-up gets shorter. “Almost done” is invalid if it is not on the report. Ontra puts the delay list next to today.ViewsList, board, and map show the same taskSwitching a view does not clone the work. Filters, tags, and assignee survive every surface so field and office talk about one card. The board is not a second Trello, the map is not a second GIS — both are lenses on the list record.ProjectProject plan: module, use case, feature, milestoneThe roadmap is not a slide — it is the tree above the task. When a milestone slips, linked work shows why the date moved. Completion percent comes from card count, not from a manager’s optimism.7 days free · no credit card
All surfaces open for 7 days: tasks, plan, sprint, document, report, and ticket. Setup takes a day; clarity starts on day one. Plans from $7.99 per seat.
