An independent student project

Connection.
Reconsidered.

Two campuses. One action. A native Mac experience designed to keep you in flow.

Watch the product film
English Campus Connect Mac interface showing separate DKU and Duke connection states and Automatic routing

Mac interface demonstration

Two campuses.
One less thing to think about.

Campus Connect coordinates independent DKU and Duke sessions, puts routing choices in one place, and stays close in your Mac’s menu bar. We are turning a recurring inconvenience into a focused, useful tool.

Meet the project.

Understand the product. Meet the mission.

English narration, original electronic score and native 0.3.12 interface captures. Connections are simulated for demonstration; authentication timing is illustrative.

Feel the difference

Less to do.
More connected.

Try the sequence. One control coordinates both campus sessions, while each keeps its own verification and status.

  1. Use your saved account
  2. Generate a fresh code locally
  3. See both campus sessions

An interactive UI illustration. Ready when you are.

Simulated states, not a real connection or speed test. Each school’s authentication and expiry policies still apply.

Campus Connect0.3.12 / DEMO
Campus Connect demonstration, disconnected

Familiar access.
Fewer repeated steps.

A workflow comparison with the standard Cisco sign-in flow described by Duke OIT.

Typical Cisco sign-in

Choose. Sign in. Verify.

  1. Open the client and select a gateway.
  2. Enter NetID and password.
  3. Choose Duo Push or enter a passcode.
  4. Complete the school verification.

Campus Connect / after setup

Connect. Keep moving.

  1. Reuse your account from local Keychain.
  2. Coordinate both campus sessions in one action.
  3. Approve Duo, or use an enrolled TOTP automatically.
  4. Pause traffic and resume while sessions remain valid.

The difference is workflow. Faster throughput and longer-session reliability still need comparable real-world validation. Duke’s Cisco MFA guidance ↗

Two connections.
Clear responsibilities.

One action coordinates both campus sessions. Each keeps its own authentication, health checks and status.

Explore the routing model

Campus resourcesCorresponding DKU / Duke session
Domestic sitesDirect, when matched by rules
Other browsingDKU PAC preferred · Duke fallback

Automatic keeps rule-matched traffic direct and prefers a ready DKU PAC exit, falling back to Duke when ready. Campus resources use their own campus session.

Interactive policy illustration. The Mac development build uses system proxies for supported TCP applications; it does not capture every app or UDP/ICMP traffic.

Native, close at hand.

Menu-bar controls stay close. Pause traffic while keeping valid school sessions, then resume without starting from scratch.

Your account, on your Mac.

Save one account to local Keychain. Approve Duo on your phone, or enroll TOTP through the official setup guide for automatic code submission.

Status with meaning.

Campus access and internet-exit readiness are checked separately. An established tunnel alone is not proof of usable browsing.

Working today.
Building what comes next.

A practical development path, with clear boundaries between implementation and verified readiness.

In development

Mac

Native interface, real dual-campus authentication, menu-bar controls, routing and local credentials. Captured operator build: 0.3.12, Apple Silicon, macOS 26+.

Sustained browsing reliability, physical network transitions and wider device acceptance remain under validation. The build is not notarized or publicly released.

Native UI preview

iPhone & iPad

Adaptive SwiftUI interfaces, account flow and configuration review are in place. Real campus authentication and VPN transport are the next engineering work.

The mobile preview does not yet establish campus VPN connections.

Planned

Compatibility & release

Improve recovery and everyday reliability. Evaluate broader operating-system support. Prepare a suitable Apple developer enrollment and a reviewed distribution path, including a possible US App Store release.

Platform support, release dates and App Store approval are not yet committed.

Forming a team

Build something
useful for our campus.

Campus Connect is an independent, student-led project. We welcome interested DKU students to build it together, whether you enjoy engineering, design, testing, or simply making campus life a little easier.

Engineering

Swift / SwiftUI, macOS, iOS and networking. Help turn the mobile preview into a real transport.

Reliability & testing

Test authentication, recovery, routing and daily use across devices and networks.

Design & communication

Make setup clearer, interactions simpler and project documentation easier to follow.

Email to join the team rw293@duke.edu

A shared effort.
A transparent budget.

Participation comes first. Voluntary support could help cover developer membership and release preparation, with an agreed budget and documented spending.

Apple lists Developer Program membership at US$99 per year. VPN apps also require appropriate organization enrollment, technical compliance and App Review. Membership funding is one step toward distribution.

Apple Developer Program ↗VPN app requirements ↗
Community references & project context

Student-built tools show how small teams can improve everyday campus life. Related projects worth exploring include VpnConnect, Gallinula’s Next Shuttle, and FedCampus. These are community references, not affiliations, endorsements or claims of collaboration.