Your MyPACS environment¶
Once payment or the trial is confirmed, we build your environment. It is not a shared account on someone else's system — you get your own server, your own storage bucket, your own database and your own user directory.
While it is being built¶
The tenant shows as Pending setup in the console. Provisioning is automatic and usually takes several minutes: a server is created, DNS records are published, the software stack is started, and TLS certificates are issued.
You can watch progress on the tenant's detail page in the console. When it finishes, the status becomes Active and the administrator receives a welcome email with the sign-in details.
Certificates can lag by a few minutes
Right after activation, a browser may briefly warn about the certificate while it is still being issued. Reload after a minute or two.
What you get¶
| Address | Purpose |
|---|---|
https://<subdomain>.mypacs.co |
Viewer — study list and image viewing, the day-to-day address for your team |
https://<subdomain>.mypacs.co/orthanc |
Orthanc — the PACS server's own interface: upload, study management, export |
https://<subdomain>-auth.mypacs.co |
Sign-in service — where usernames and passwords live |
Substitute your own subdomain. All three are also shown on the tenant page in the console.
What runs inside¶
- Orthanc — the DICOM server that indexes and serves your studies.
- PostgreSQL — the index of studies, series and instances. Images themselves are not stored here.
- Object storage — a private S3 bucket holding the DICOM image data, one bucket per customer.
- Keycloak — your own user directory and sign-in service, holding only your users.
- Viewer — a MyPACS-branded OHIF viewer, signed in through Keycloak.
First sign-in¶
Sign in at https://<subdomain>.mypacs.co with the administrator email address
you gave when creating the tenant, and the temporary password from the welcome
email. You are asked to set a new password immediately.