Skip to content

One Hub for the whole program.Each partner sees only its files.

DekkoCORE gives biotech and pharmaceutical companies one end-to-end encrypted place to share a drug program with the partners who move it forward: university labs, CROs, contract manufacturers, trial sites, safety boards and licensing partners. Each partner sees only the files shared with it, at the level you set, for as long as its agreement runs, and every view and download is recorded.

EXB-214 program HubDrawn as a plate map

In DekkoCORE

Row
A partner you invite to the Hub
Column
A file in the Hub
Well
The access you set when you share
See the Hub as

How to read it

The plate is your program's Hub.

Before a run, a scientist fills in a plate map: what goes in every well. We've drawn a DekkoCORE Hub the same way. Each row is a partner you invite to the Hub, each column is a file in it, and each filled well is a partner that can open that file, at the level you set when you share it. Row A has a gap at column 10: your own team can't open the unblinded tables.

Without a Hub, unpublished results and process know-how travel as attachments. One forward too many can cost a patent its novelty, and an email can't be called back.

Rows: partners in the Hub

A
Your team. Example Bio's R&D and program team
B
University lab. An academic collaborator under a research agreement
C
Assay CRO. A contract research organization running the binding assays
D
Tox CRO. A contract research organization running the toxicology studies
E
CDMO. A contract manufacturer making the clinical batches
F
Trial sites. The investigator sites running the Phase 1 trial
G
Safety board. The independent data safety monitoring board
H
Licensing partner. A pharmaceutical company reviewing the program for a license

Columns: files in the Hub

  1. 1target_validation_summary.pdfDiscovery
  2. 2lead_series_SAR.xlsxDiscovery
  3. 3binding_assay_protocol.pdfDiscovery
  4. 4binding_assay_results.xlsxPreclinical
  5. 5GLP_tox_report.pdfPreclinical
  6. 6process_description_v2.pdfManufacturing
  7. 7batch_record_B003.pdfManufacturing
  8. 8phase1_protocol_v3.pdfClinical
  9. 9investigators_brochure_v2.pdfClinical
  10. 10interim_unblinded_tables.pdfClinical
  11. 11data_package_summary.pdfPartnering
  12. 12regulator_meeting_minutes.pdfPartnering

Wells: the access you set

  • ManagerYour team, running the program's Hub
  • DownloadOpen the file and keep a copy
  • View onlyRead it in the secure viewer, with nothing to keep
  • Submission linkSend files in, without seeing what's there
  • EmptyThe partner can't open the file, or see it

Manager, Download and View only are three of the seven levels in DekkoCORE's Share dialog. A submission link lets a partner send files in without an account.

One program

From the first compound to the license.

Follow EXB-214, a fictional compound at Example Bio, from discovery to a licensing deal. Each partner's wells fill as the program reaches it, beside the DekkoCORE screen that does each step.

EXB-214 program HubAs the program runs

Run sheet · EXB-214

  1. Step 1 · Discovery · Month 0

    Early data goes to the university, View only.

    With: University lab

    Example Bio shares the target validation summary and the lead series with a university lab under a research agreement. The lab reads them in the secure viewer, under a handling banner, with access that ends when the agreement does. There's no attachment to forward, so unpublished results stay unpublished.

    • View only, in the secure viewer
    • A handling banner on every page
    • Access that ends with the agreement
    A PDF open in the DekkoCORE secure viewer, under a red banner that reads This is an EXPORT CONTROLLED workgroup
    In DekkoCOREThe secure viewer: the file opens in the browser, under the Hub's handling banner.
  2. Step 2 · Preclinical · Month 4

    The CROs send results in, and see nothing else.

    With: Assay CRO and Tox CRO

    The assay CRO downloads the protocol it needs and sends its results back through a secure submission link. So does the toxicology CRO, with no account needed. Each file lands in its own folder, encrypted before it leaves the sender's device.

    • Submission links that need no account
    • No file size limits
    • Uploads scanned for malware
    A DekkoCORE Hub's file list, with a folder named 5 July Submissions marked Submission ON
    In DekkoCOREA folder with submissions turned on: partners send files in through a secure link, without an account.
  3. Step 3 · Manufacturing · Month 9

    The process goes to the manufacturer, and stays yours.

    With: CDMO

    The process description is the program's hardest-won know-how. The CDMO reads it View only and sends executed batch records back through a submission link. If the relationship ends, revoke the share and the process description is gone from its view at once.

    • View only, with nothing to download
    • Revoke a share instantly
    • Every view recorded against the file
    The DekkoCORE share dialog for one file, with one recipient set to View only and another to Download
    In DekkoCOREThe Share dialog: each person gets their own level, View only for one and Download for another.
  4. Step 4 · Clinical · Month 14

    Sites get the protocol. Only the safety board gets the unblinded data.

    With: Trial sites and the safety board

    Investigator sites download the protocol and read the investigator's brochure View only. The unblinded statistician's interim tables go to a folder shared only with the safety board, View only, for the weeks of its review. Your study team isn't given access, so the blind holds, and the file's history shows it did.

    • Seven permission levels
    • Expiry dates on every share
    • A record of everyone who opened the file
    The DekkoCORE share dialog with a Set expiry date link and a recipient's permission menu open at Listing only, View only and Download
    In DekkoCORESeven levels, from Listing only to Full permissions, and an expiry date on the same share.
  5. Step 5 · Partnering · Month 20

    A licensing partner reviews the package, for as long as the CDA runs.

    With: Licensing partner

    A pharmaceutical company considering a license reads the data package and the regulator meeting minutes View only. It can't see the CROs, the sites or anyone else in the Hub. When the confidentiality agreement ends, so does its access, and the file history shows what it read.

    • Partners can't see each other
    • Access that ends on the date you set
    • File history of every view and download
    DekkoCORE file history for one PDF, listing each event with its date and user, with an Export button
    In DekkoCOREFile history: every view, download and approval, with the date and the person, ready to export.

The record

Every view, download and upload, on the record.

Every view, download and upload is logged against the file, with the person, the date and the time. Export a file's history for an inspection or a licensing negotiation, download the tenancy's audit log as CSV, or stream it to your Log Analytics workspace.

DekkoCORE audit logs for one Hub: each user's views, downloads and uploads with the date, a period filter and a Download as CSV button
Audit logs in DekkoCORE. Activity across the Hubs in your tenancy, filtered by Hub and period, ready to download as CSV.

Protections

What your security and legal teams will ask.

  • Zero-knowledge, end to end

    Files are encrypted on the device that uploads them. DekkoSecure can't open your compound data, and neither can anyone outside the share.

  • Partners walled off

    Partners join as External Members. They see your team, never each other, and only the folders shared with them.

  • Hosted where your agreements say

    DekkoCORE is hosted in-country in Australia, the United States and Canada.

  • IRAP assessed

    Assessed for Australian government information up to PROTECTED.

  • Sign-in you can enforce

    Two-factor authentication, passkeys with hardware attestation and single sign-on for everyone in your tenancy.

  • Uploads checked for malware

    Malware scanning, where the add-on is on, checks files from partners as they arrive. Infected files can't be downloaded or shared.

Questions

Asked by R&D, legal and security teams.

Does DekkoCORE replace our ELN, LIMS or eTMF?

No. Your validated systems stay the record. DekkoCORE handles the files that move between you and your partners: protocols and process documents going out, results and batch records coming in, and unblinded data going only where it should.

Can our CROs see each other?

No. Partners join your Hub as External Members, who see your Team Members but can't see or contact other External Members, even when the same file is shared with them.

How do we share IP without a partner keeping a copy?

Share it View only, so it opens in the secure viewer with nothing to download, under a handling banner, with an expiry date that matches the agreement. No system can stop someone photographing a screen, but View only leaves no file to forward, and every view is recorded.

Can a CRO send us results without an account?

Yes. Share a secure submission link or QR code, which needs no account. For partners you work with throughout a program, share with their own account instead.

How do we keep unblinded data from our own study team?

Share the folder only with the unblinded statistician and the safety board. Your study team isn't given access, and the file's history shows everyone who opened it: the evidence that the blind held.

Do partners need a DekkoSecure subscription?

No. Partners are invited by you and register a DekkoSecure account to take part. Their own organization doesn't need a subscription.

Where is program data stored?

In-country in Australia, the United States or Canada, so data can stay where your agreements and approvals require.

Bring us your partner list.

Tell us who works on one of your programs and how files reach them today. We'll set it up as a Hub, with a folder for every partner and the access each one needs.