Skip to content

Built and maintained by your administrator

One private home for every tool your team uses

The tools are already built, checked in a real browser and waiting. You sign up, and every one of them opens for seven days - no card, nothing to install. Subscribe and your whole team keeps them, with the rights and the audit log that go with sharing.

Share by code
Every account has a short code. Type it and the person is in.
Rights per person
Share further, manage rights, see the log, remove access - all on by default, narrowed when you like.
An audit log
Every open, edit and share, with a name and a time, kept as history.

To add somebody to a team

1 code

Their share code, typed once - nothing to email around

Logins per person

1

Every tool signs in as the same portal user

Public tool addresses

0

Files live outside the website, behind a checked door

Recorded in the audit log

Everything

Opens, edits, shares, rights changes and rollbacks

How it works

Three steps, and the middle one is the hard part

Adding a tool is a two-minute job. What happens in between is what keeps your people and your files safe.

  1. 1 About a minute

    Drop the file in

    A single .html file. Give it a name and a plan tier. It goes straight into a private folder - not a website folder.

    • No build step, no server to run
    • Add it yourself if a team grants you Create
  2. 2 Runs itself

    The portal checks it

    A hidden Chromium opens the tool exactly as a user would receive it, watches for JavaScript errors, confirms the page really renders, takes a screenshot and fingerprints the file.

    • Anything broken is held back with the exact reason
    • The tool's own password screen is removed here
  3. 3 Your call

    You decide who, and what they may do

    Share with a team, or with somebody's personal code. Everybody starts with create, edit, archive and delete; narrow any of them for one person whenever you want.

    • Optional end date on any share
    • Archive it without losing the history, or delete it completely

Teams & sharing

Give a tool to five people in one move - then tune it per person

Nobody types a username again. Every account has its own 8-character share code, and a person can sit in as many teams as their job needs. Rights are set once for the team, then adjusted for anybody who is different.

Add somebody with their code

Type a colleague's 8-character code and they join that team instantly. Codes are generated with the account, are unique, say nothing about the person - and a fresh one can be issued at any time.

One person, many teams

Finance, Legal, a client project - each team keeps its own member list and its own tools. If two teams both share the same tool, the person keeps the widest set of rights, so nothing narrows behind their back.

Two policies, one screen

Team policy is what every member inherits the moment they are added. Person policy is the exception: change one member's rights and everybody else stays exactly as they were - with a note saying why.

A log that cannot be edited

Who joined which team, who opened which tool, who changed which field and who widened whose rights - recorded with a name and a timestamp. Each tool keeps its own history, and every edit keeps the version it replaced.

What you get

The boring safety work, done for you

None of this is decoration. Each item is something you would otherwise have to build, remember or explain yourself.

Private by default

Tool files live outside the website. There is no public link to guess, and no folder to browse.

Checked before release

Every upload is opened in a real browser, screenshotted and screened for errors before anybody can use it.

Teams in one click

Add a colleague with their share code, group people into teams, and share a tool with the whole team at once.

Rights per person

Share further, manage rights, see the log and remove access are decided per tool, per team and per person - and you can change one person without touching the rest.

Built for full-size work

A tool opens as its own page, so wide spreadsheets, canvases and side-by-side panels keep the layout they were built for.

One login, always

The tool's own user ID and password screen is removed on upload, so nobody manages a second set of credentials.

Every open is logged

Grants, uploads, audits, edits, shares and opens are written to an audit log that cannot be edited afterwards.

History you can undo

Every edit keeps the version it replaced, with who changed it and why. Put an earlier version back in one click.

Privacy & checks

Three promises about your tools, in plain English

A tool is only as private as the door in front of it. These are the three things this portal gets right, and how.

It opens as its own page, never inside a frame

Putting a tool in a frame clips its layout, blocks its pop-ups and confuses its keyboard shortcuts. Here it opens as a normal, full-width page, so a wide spreadsheet, a canvas or a side-by-side panel behaves exactly as it was built to.

The page also states that it refuses to be framed, cached, indexed or archived - by anyone, including search engines.

One login, because the tool's own one is removed

If a tool arrives with a user ID and password screen, that screen is stripped out when the tool is added: password fields become inert, stored passwords are emptied, and the portal signs the tool in as the person who opened it.

If a tool cannot be signed in that way, the portal refuses it rather than leaving a half-broken login in front of your users.

The file itself is unreachable

Tool files are stored in a private folder the web server does not serve. There is one door - a permission-checked view - and it asks five questions before it reads a byte: are you signed in, were you given this tool, does your plan cover it, is the file unchanged, and can the tool be signed in.

A copy someone saves by hand refuses to run, and every released page carries a quiet watermark naming who it was served to.

What you can see

  • Who you shared each tool with, what they may do, and until when
  • Who is in each team, what they were added as, and who added them
  • Every open, edit, share and rights change, with a name and a time
  • The version history of every tool, with one-click rollback

What nobody can do

  • Turn a failing tool into a live one by hand
  • Read a password a tool used to have - those are emptied, not stored
  • Hand a file to somebody outside the portal without leaving a trace
  • Edit or delete a line in the audit log - not even an administrator

What you can host

Any browser tool fits

If it runs in a browser, it belongs here. Nothing is tied to one industry or one file type - the portal is the shelf, your tools are the books.

  • Calculators
  • Converters
  • Checklists
  • Dashboards
  • Viewers
  • Generators
  • Planners
  • Internal forms
  • Estimators
  • Reference lookups
  • Quotes & proposals
  • Print layouts

Anything that saves work stores it against the signed-in user, so two people using the same tool never see each other's records.

Sales & proposals

One quotes-and-estimators shelf the whole desk uses, with a log of who opened what and which version they were working from.

Operations

Give each team its own tools and its own rights. Nobody sees a tool they were not given, and the audit log answers the awkward questions.

External clients

Hand a client their own corner without emailing a single file, and end an engagement by removing them from the team.

Training & onboarding

One login, every exercise in the same tidy place, and a new joiner added with a single code on their first morning.

Plans

Everything for 7 days, then the plan you keep

Every account starts with the demo: every published tool, open for seven days, no card and no checkout page. After that, a plan keeps the tools open and adds the parts a team needs - teams and share codes, per-person rights, and the audit log. Your administrator switches plans on.

Free for 7 days

7-day demo

$Free for 7 days, no card

Everything unlocked for 7 days from the moment you sign up.

Best for: Finding out whether this fits how your team already works

  • Every tool your administrator has published
  • Seven days from signing up, no card and no commitment
  • Your own private dashboard and audit trail
  • Download everything you saved, whenever you like
Share tools
Included
Teams
Included
Exports
Included
Calendar feed
Included
Audit log
Included
API access
Included
Webhooks
Included
  • People per team: No limit
  • Exports per month: No limit
  • API tokens: No limit

Not included

  • Seven days, then it ends
Start my 7-day demo

Starts the moment you sign up. Nothing to cancel.

Everything, no limits

Pro

$49 per month

Everything, including the advanced tools.

Best for: Power users who need the advanced, heavier tools

  • Everything in Basic
  • Pro-tier tools
  • Priority help from your administrator
  • Webhooks so alerts land in Slack or Teams
  • First to get new tools
Share tools
Included
Teams
Included
Exports
Included
Calendar feed
Included
Audit log
Included
API access
Included
Webhooks
Included
  • People per team: No limit
  • Exports per month: No limit
  • API tokens: No limit
Ask for Pro

Your administrator switches plans on, usually the same day. No card to enter here.

Compare every plan side by side on the plans page, or ask your administrator to move you up - it takes them a few clicks.

Questions

Answered the way we would answer a colleague

What is the Tool Portal for?

It is one private home for the browser tools your team relies on - calculators, converters, checklists, viewers, generators, small internal apps. Instead of emailing files around and hoping everyone opens the right version, people sign in once and open what they were given.

How do I add somebody to a team?

Every account has its own 8-character share code. Type somebody's code on a team page and they are in - no email addresses to hunt for, no user IDs to guess. A person can belong to as many teams as they need, and each team keeps its own member list and its own tools.

Who is allowed to change a tool?

Only your administrator. Tools are added, updated, archived and deleted by whoever runs the portal, so what a team is given is what everybody gets. What a team *can* control is the audience: who else receives a tool, what each person may do with it, who can read the log, and who can take it away again.

Do users need a second login for each tool?

No. If a tool arrived with its own user ID and password screen, the portal removes that screen when the tool is added and signs the tool in as the person who opened it. One login, for everything.

Can someone get a tool file without permission?

No. Tool files are stored outside the website folder, so there is no address that serves them, and the only door is checked against your account, your plan and the tool's own integrity every single time. A copy saved to disk refuses to run.

What if somebody changes a tool and we prefer the old version?

Every edit is kept as a numbered version with the values it replaced, the person who made the change and their note. One click puts an earlier version back - and the rollback is recorded too, so nothing disappears quietly.

How do I see who did what?

Every share, rights change, edit, archive, delete and open is written to an audit log with a name and a timestamp. Each tool has its own history page, and there is a wider log across everything you own or share in. Log entries cannot be edited or deleted - not even by an administrator.

What happens when somebody leaves?

Remove them from the team and they lose exactly what that team shared, straight away. Anything granted to them by name stays until you take it away, and the record of what they did is kept either way.

What happens if a tool is broken?

It never reaches your users. Every tool is opened in a hidden browser first, and anything that errors, loads blank or fails the checks is held back with a plain-English explanation for whoever added it.

Where is my data stored?

Anything a tool saves is kept against your own account, and you can download all of it as a JSON file from your account page whenever you like.

What happens on day eight?

Your demo ends and the tools close, because that is what a demo is. Nothing is deleted: your account, your saved work and your history stay exactly where they are, and a subscription - or seven more days from your administrator - opens everything again.

How do I change my plan?

Ask your administrator, or use the See the plans button on your dashboard. They can move you between the demo, Basic and Pro in a few clicks, and the tools you are allowed to open update straight away.

Still unsure? Email saadanwer83@yahoo.com and a human will answer.

Everything you need is already set up

Create an account and every tool opens for seven days. Add the people you work with using their share codes, and put your team's tools in one place.