Skip to content
PresencebyAnimweb Technologies

Running Presence on your own domain

How a converted workspace moves to a dedicated deployment on your university's domain - for IT teams.

4 min read

Paid institutions can run Presence on their own domain - for example attendance.university.edu - with their own database. The application is the same one you used in the demo; your workspace moves across unchanged.

What you get

  • The Presence app on your domain and the API on a sub-domain of it (for example api.attendance.university.edu).
  • Your own MongoDB database (we can host it, or use your institution’s Atlas project).
  • A signed license that sets your plan, student seats and validity. Renewals are a new license key - no downtime and no data changes.

The move, step by step

  1. Request it. After converting, open Billing → Move to your own domain and enter the domain you want.
  2. DNS. Your IT team creates two DNS records we send you (one for the app, one for the API). Both must be under the same registrable domain so sign-in cookies stay first-party.
  3. We deploy. We set up the app and API with your license. On our hosted option the API runs on Railway: API servers with PROCESS_ROLE=web and a separate worker service with PROCESS_ROLE=worker, a Railway Redis service, settings held in Railway Variables, and more replicas added as your load grows. The database runs on MongoDB Atlas.
  4. Export. An administrator opens Billing → Export your workspace. You download one encrypted .pexport file and see a one-time passphrase. Keep both safe.
  5. Restore. On the new deployment’s first-run setup page, the export file and passphrase restore every user, class, attendance record and Face ID. (Face templates are re-encrypted with the new deployment’s own key.)
  6. Sign in with Google (optional). We register a Google client for your new address, or your IT team does following Setting up Sign in with Google. Your Google setting and allowed domains carry over in the export.
  7. Switch over. Share the new address. Everyone signs in with their existing credentials - the institution code field is no longer needed.

The first-run setup page works only while the new deployment is empty and, in production, only with the one-time setup key we give you. It closes for good once your workspace is restored. See Setting up a new campus, step by step.

Responsibilities

Animweb Your IT team
Application updates and security fixes ✓
License issuance and renewal ✓
DNS records for your domain ✓
Database hosting ✓ (default) ✓ (if you prefer your own)
Access policies for your staff and students ✓

Requirements

  • A domain you control and the ability to add DNS records.
  • HTTPS is provided automatically.
  • No servers to maintain on your side unless you choose to self-host the database.
  • The domain name itself is not included in any Presence plan: your institution registers and renews it. A sub-domain of your existing domain costs nothing extra.

Running on your own servers

If your institution chooses to run Presence on its own infrastructure (see Plans and pricing), plan for the following. The sizes are a starting point; we confirm them with your IT team before installation.

Tier (peak students) API servers Database (MongoDB 7 or later, 3-member replica set) Cache Background workers
Tier C (15,000) 3 x 4 vCPU, 16 GB RAM behind a load balancer 4 vCPU, 16 GB RAM each Redis 7, 5 GB 1 x 2 vCPU, 4 GB RAM
Tier B (25,000) 5 x 4 vCPU, 16 GB RAM behind a load balancer 8 vCPU, 32 GB RAM each Redis 7, 10 GB 2 x 2 vCPU, 4 GB RAM
Tier A (40,000) 8 x 8 vCPU, 32 GB RAM behind a load balancer 16 vCPU, 64 GB RAM each Redis 7, 20 GB 3 x 4 vCPU, 16 GB RAM

Database storage should hold your data with room to grow and fast SSD disks. API servers run with PROCESS_ROLE=web and workers, as a separate service, with PROCESS_ROLE=worker.

  • Software: Linux (Ubuntu 22.04 or 24.04 LTS recommended), Node.js 24 LTS, a reverse proxy with HTTPS (for example nginx) that passes WebSockets.
  • Network: HTTPS (443) reachable by students’ phones on mobile data; the database and cache reachable only from the application servers; outbound internet for updates and email.
  • Backups: daily database backups kept for at least 30 days and stored away from the database servers. Your IT team owns backups on this option.
  • Access: a secure way (for example a VPN or bastion host) for our engineers to install updates and investigate issues.

Questions? Contact us.