See how your product team is really doing
ShipWoven is the operations portal for startups: daily reports your leads sign off, a roadmap that shows what you are working on now, Jira in both directions, an issue flow, fair points, and a zero-knowledge vault for the keys, payments and contracts you cannot afford to leak.
- Set up with you, adapted to how you work
- Encrypted in the browser
- Works on any phone
Key facts
- Runs on
- Cloudflare's edge, one isolated database per company
- Secrets
- Encrypted in the browser, never readable by the server
- Jira Cloud
- Two-way: statuses and comments from the portal
- Organisation
- Departments, teams and four levels of access
- Setup
- Done with you, customised to your process
Standups don't scale. Spreadsheets don't sign off.
Past ten people, founders stop seeing the work. Status lives in chat, the roadmap lives in someone's head, and the production keys live in a pinned Slack message.
Reports nobody reads
Updates pile up in a channel with no owner. Nobody knows who worked how many hours on what, and nobody signs off that the work is real.
A roadmap nobody trusts
Jira says 0% until the last ticket closes. The real plan is a slide from last quarter, and "what are we working on?" takes a meeting to answer.
Secrets in the wrong places
API keys in a shared doc, the company card in a chat, contracts in someone's inbox. One leaked laptop and it is all gone.
One portal for the work, the plan and the keys
Six modules that share one organisation, one access model and one phone-first interface.
Built like infrastructure, not like a dashboard
Four levels. Each one sees exactly what it should.
Access flows down from departments to teams to people, and up from members to their leaders and managers. No role sees more than its part of the company.
The whole company
Founders and operations leads.
- Every department, team and person
- Forms, policies, workflows, integrations
- Signs reports when nobody above the author can
- Verifies payments, holds the recovery keys
One department
Head of engineering, head of product.
- All teams and people in the department
- Signs their leaders' reports
- Plans epics and sets what the department is on
- Resources the department was given
One team
Tech leads, squad leads.
- Their team's reports and performance
- Signs their members' reports
- Moves their members' Jira tickets
- Everything their members have
Themselves
Engineers, designers, QA.
- Their own reports and tickets
- What the company works on now, with their tickets first
- Shared docs and credentials they were given
- Their score, once the team is shown it
The parts a growing company needs next
Your organisation, drawn
Departments with managers, teams with leaders, people with roles, on an organisation chart that folds and unfolds. Access to projects, forms and resources is given to a department and reaches everyone in it; a team or one person can be given more, less or nothing.
Organisation and access →
Credentials, payments and contracts the server cannot read
Shared logins, API keys, the company's payments with their receipts, and legal documents such as NDAs, employment contracts and passports are encrypted in the browser under keys derived from each person's password. Access is per section and per person: read, comment, write, verify. Every reveal is recorded.
- Recovery kit per person, key rotation when someone leaves
- Finance month by month, receipts, verification, bulk edit, import and export
- Legal: company details, dates, expiry flags, encrypted notes, badges on People
Configured in the product. Customised with you.
Most of what makes a company different lives in forms, stages and rules. All of them are yours to change. For the rest, we build it.
Tell us how you work
Who reports to whom, what a daily update should ask, how a bug moves to done, what counts as a good week.
We set it up with you
Departments, teams and people imported, forms and policies written, Jira connected and projects chosen, the vault enrolled.
Your leads run with it
We walk them through the first week of reports, sign-offs and the roadmap. Anything missing goes on our list, and often ships within days.
Zero-knowledge is not a feature. It is the design.
Secrets are sealed in the browser and wrapped for each person who may read them. The server holds ciphertext and public keys, and that is all it will ever hold.
In your browser
with your key
What the server keeps
- Keys derived from each person's password, never sent to the server
- Every reveal, edit and verification in an audit trail
- Access per section: none, read, comment, write, verify
- Rotation when someone leaves, re-wrapping when someone joins
- Recovery kits instead of back doors
- Self-hostable when your policy requires it
Questions people ask
Who is ShipWoven for?
Startups and product companies with 5 to 200 people who want to know how their engineering, design and QA teams are really doing, without more meetings. It fits remote and hybrid teams, agencies running several clients, and companies working with an outsourced development team.
Do we need Jira?
No. Reports, the roadmap of what you work on now, the issue flow, points and the vault all work on their own. Connect Jira Cloud when you want epics and stories synced, statuses changed from the portal, and progress computed from your own Jira statuses.
What does zero-knowledge mean here?
Credentials, payments and legal documents are encrypted in your browser with keys derived from each person's password. The server stores only ciphertext, public keys and who may read what. Nobody at ShipWoven can read your secrets, and neither can an attacker who takes the database.
Can it be customised for our company?
Yes. Report forms, issue forms, workflow stages, points policies, progress policies, schedules and access are all configurable in the product, and we adapt the setup with you. When you need something the product does not do yet, we build it.
Where does it run?
On Cloudflare's edge. Each company gets its own address, like yourcompany.shipwoven.com, and its own isolated database, so your data never shares a table with another customer. It can also run on your own server as a plain Node.js application.
How do we start?
Tell us about your team on the contact page. We create your workspace at yourcompany.shipwoven.com and send your first super admin a setup link that only their email can use. Then we import your people and projects, adapt the forms and policies to how you work, and walk your leads through the first week.