01Family, together
For a bedridden or device-unable loved one. Approved family on separate screens.
Family & group access
- Family visits and group-call experiences are planned; actual visitor video is unavailable.
- Real accounts, own households, family/professional-caregiver roles and household-scoped administrator permissions work. Recipient acceptance does not replace patient or legal-representative setup approval.
- In-app accept/decline, expiry, renewal, revoke and leave controls work; no invitation is sent. No public guest token can grant household or camera access.
Visits on their terms
Planned family watch shifts, visiting hours and two distinct privacy choices.
Permissions, schedules & DND
- Visiting and do-not-disturb settings, single check-in versus continuous-connection requirements and timezone-aware shifts genuinely save.
- Assigned access, amendment/cancellation history, revocation and expiry are enforced by the portal.
- Schedules are requirements, not proof of check-in, attendance or attention. Actual attendance remains unknown / not connected.
- Proposed DND modes: full privacy blocks all remote access; separately approved quiet look-ins would allow viewing without ringing or starting conversation, never hidden access or a bypass of full privacy. Quiet mode is not built; current DND behavior is unchanged.
A thoughtful handover
Family handoffs, with feeding schedules, shared discussion and private threads proposed.
Notes, summaries & inbox
- Authorized timestamped notes, role-restricted administrator summaries and manually requested in-app review items genuinely save.
- Own assigned workspace remains separate from administrator summaries and other people's notes.
- Acknowledged means seen, not resolved. Resolving or cancelling a review is a separate recorded action. No external notification is sent.
- Feeding schedules/logs, persistent family discussion and selected-member private threads are proposed, not a built chat or feeding-log product. Audience, retention and access controls must be explicit.
Help when a visit is missed
A planned human follow-up chain, not a claim that someone is watching.
Reminders & backup people
- Planned due-soon reminders, primary then backup escalation, SMS and phone follow-up need explicit permissions and human acknowledgment.
- Private dry-run queue logic is tested with fixtures only. No reminder, email, text, call or emergency response is delivered.
- Unknown/offline device, missing visitor, DND, late/within-grace, recovery, denied access and delivery failure are distinct planned states. Acknowledgment is not recovery or resolution.
A place for organizations
Hospital, senior-living and convalescent-care concepts, without overstating readiness.
Planned corporate controls
- Organization accounts, facility/site/room/tenant boundaries and enrolled bedside devices are planned requirements, not deployed enterprise capabilities.
- Visiting hours and caregiver assistance must respect patient wishes and approved representative permissions.
- No institution customers, endorsements or clinical/compliance capability are claimed.
Honest connection states
Clear privacy and failure states, not false green reassurance.
Device & access boundaries
- Logical device enrollment, approval attestations and visitor grants can save; they do not prove a physical device is online or ready.
- Planned connection/reconnection, privacy pause, revoked consent, stale permissions and device power/network failures must remain distinguishable.
- All public animation is fictional. Real visitor media is server-disabled; no continuous coverage or attention inference exists.
- Medical-device readings are exploratory only. No compatible device, clinical alert or equipment control is available. See the proposed plan for consent, safety and interface boundaries.
Clear limits, from the start
What's real. What's next.
What genuinely works now?
Signup/login, a bot-protected waiting list, own households, accepted role-scoped access, saved schedules/settings, authorized notes and in-app reviews, logical enrollment and manual guided checklists. Email addresses remain unverified; email verification and password-reset delivery are not available.
Is this a live camera or working video-call service?
No. The illustrations are simulated, silent and local to this page. Actual video is not enabled, and physical iPad or cross-network video reliability has not been established. No camera or microphone is requested and no recording, upload or message is sent.
Does this replace care or prove someone is paying attention?
No. Bedeye is not medical care, clinical monitoring or emergency response. A connection or scheduled assignment cannot prove human attention. Browser backgrounding, locks, networks, battery or power loss can interrupt devices; continuous availability and 24/7 reliability are not guaranteed. For an emergency, contact local emergency services.
Can a hospital or facility use corporate accounts today?
Institutional accounts, tenant/room permissions and facility workflows are planned concepts, not deployed enterprise services. Patient wishes and privacy must remain authoritative, with caregiver/representative configuration only within approved permissions. No institution adoption or endorsement is claimed.
A family experience. A reason to build.Why I’m building Bedeye
My wife and I cared for an elderly, bedridden loved one in our home. We kept bringing our phones into the room for FaceTime with relatives. When we weren't there, family couldn't get in touch. I imagined a bedside device with approved access, visiting hours and optional scheduled look-ins. Bedeye is something we didn't have when our family needed it. I'm in the process of building it.
John Venti · Founder