Questions

Drox is document control and project delivery for solar, BESS and grid-connection projects: the document register, transmittals, review and markup, RFIs and correspondence, tasks and the programme, and a field app for forms, inspections and quality on site.

Engineering consultancies, EPCs and developers running projects with people from several companies: your own team, the client, the contractor and the owner's engineer, each on the same project and each seeing what is theirs.

Yes. It installs on a phone from the browser. Forms filled with no signal are kept on the phone and sent when it reconnects, and drawings can be saved to the phone to open on site.

It reviews drawings and documents and reports findings, compares revisions, and answers questions about your project. When it proposes to create or change something, a person confirms it first.

AI is off for an organisation until it is switched on, and an AI action shows what it will cost before it runs.

Yes. A register in Excel or CSV is imported in one pass, each row with its own document number and classification. Rows that cannot be imported are listed with the reason rather than stopping the rest.

No. People invited to a project from another company, such as the client, the contractor or the owner's engineer, join as guests. Guests are free and do not count towards your plan's members on a project.

Only what has been shared with them. Controlled documents, transmittals and project folders start visible to the project's admins only, and are shared with a company or the whole project deliberately. A guest cannot open your organisation's contacts, settings or other projects.

Pricing is agreed with you after a demo, based on how many projects you run and how you work.

Drox's database is hosted with Amazon Web Services in Sydney, Australia. Project files are kept in Drox's storage, or in your organisation's own SharePoint or Dropbox if you connect one.

Passwords are stored only as bcrypt hashes. A signed-in session token is valid for an hour at a time. Sign-in, sign-in codes and password resets are rate-limited, and every sign-in and failed sign-in is recorded.

The site is served over HTTPS only (HSTS), with a content security policy, and other sites are not allowed to frame it.

Your project admins. Everybody on a project belongs to a company on it, and records are shared with the whole project or with chosen companies. Access is checked on the server for every request, not only hidden on screen.

Only a project admin, and a deleted document goes to a recycle bin with its number, history and files, restorable whole. Erasing it for good needs a code emailed to that admin and then waits thirty days, during which it can still be restored.

A revision that has been issued or reviewed cannot be deleted at all.

A signed document is sealed with a key held in AWS Key Management Service that cannot be exported, so a sealed file cannot be altered without it showing. The signing certificate lists the SHA-256 fingerprint of each signed file.

Yes. Sign-ins, access granted or removed, role changes and invitations are recorded in a security log, and every project keeps an activity register of what happened to its records and who did it.

Book a demo: a live walkthrough with one of the team, on a project like yours. We agree pricing and the next steps from there.

No. A project starts from a template holding its roles, stages, tasks, register and forms, and you fill each role with a person or a team once.