Skip to content
DryNight signal before wetness

Technology

The technical story should get sharper the closer you read.

DryNight is evaluating whether a lower-abdomen wearable can estimate bladder filling early enough to trigger a private cue before wetness starts. Ultrasound is the current lead, but the work stays focused: test the signal, test the form factor, then build the architecture around what families can actually use.

This page describes product direction and evidence posture, not validated product performance.

Product thesis

Measure bladder state, then decide whether an alert is justified.

The core technical question is narrow: can a lower-abdomen wearable generate a stable enough estimate of bladder filling to support a private pre-void cue? Ultrasound is the lead candidate because published research has explored wearable bladder monitoring. Bioimpedance and adjacent modalities remain open until bench and overnight data show what survives real use.

01

Signal discipline

  • Estimate bladder filling conservatively
  • Separate raw signal from family alerts
  • Treat uncertainty as a product state
02

Family experience

  • Keep setup brief before bed
  • Cue the wearer privately first
  • Escalate to caregivers only when configured
03

Evidence posture

  • Show external precedent without overstating equivalence
  • Run feasibility before marketing
  • Keep regulatory language explicit

01

Start with pediatric nocturnal enuresis, then adapt the same timing problem for adult and older-adult care

02

Treat ultrasound as a lead hypothesis, not a settled hardware verdict

03

Evaluate candidate modalities on signal specificity, comfort, power, and manufacturability

04

Keep the first architecture centered on a cordless patch and private haptic cue

05

Move the minimum necessary information downstream to family devices

06

Let feasibility evidence decide whether the concept scales, pivots, or narrows

System architecture

A more believable technical story starts with the signal path.

DryNight is not presenting a finished device architecture. It is showing the working structure serious partners would want to interrogate: body interface, sensing modality, on-device estimation, and private alert delivery.

DRYNIGHT CONCEPT SYSTEM Technical architecture under evaluation Feasibility-first, pre-prototype, privacy-aware 01 BODY + PATCH Skin contact, placement, motion The physical interface has to survive an entire night before any sensing approach is credible. 02 SENSING + INFERENCE Analog front end + candidate transducer Ultrasound leads today; alternatives remain open until data says otherwise. On-device estimation layer Convert repeated measurements into a conservative bladder-filling estimate, not diagnosis. OUTPUT: confidence band + alert threshold Decision logic Only escalate when signal stability, timing, and family preferences justify a cue. 03 PRIVATE OUTPUTS Child wristband Quiet haptic cue first No public audible alarm by default 04 FAMILY / RESEARCH LAYER Caregiver device Receives minimal event state only when family settings allow escalation. Research telemetry Handled separately, under explicit study consent, rather than bundled into routine family use. Principle: prove signal quality before scaling software language. Principle: separate family alerts from research data exhaust.
Concept architecture only. The specific sensing stack, signal-processing split, and device boundaries will change if feasibility work shows that another modality or another data path is more honest and practical.

01

Body interface

A soft lower-abdomen patch has to maintain contact through sleep, movement, and body-position changes before any signal promise matters.

02

Sensing stack

Ultrasound is the lead candidate, with adjacent modalities held open until bench work shows which path best balances signal quality, comfort, power, and cost.

03

On-device logic

The first useful model is not diagnostic AI. It is a narrow estimate of whether the bladder is filling consistently enough to justify a threshold alert.

04

Private outputs

A child wristband and optional caregiver device should receive only the minimum event information needed to act, not a stream of intimate raw data.

Architecture rules

  • Feasibility first

    No sophisticated product layer matters if the abdomen signal is weak, unstable, or too power-hungry for overnight wear.

  • Minimal data path

    The architecture is being framed to keep raw sensing close to the patch and move only threshold-level outputs downstream.

  • Family-safe failure modes

    If the system is uncertain, it should degrade conservatively instead of pretending precision it has not earned.

Feasibility path

The next evidence is sequential, not assumed.

Serious readers should be able to see the proving path immediately: first establish that a usable signal exists, then show the system can survive real nights, then decide whether broader validation is warranted.

  1. Stage 01

    01

    Bench signal screening

    Decision question: Can any noninvasive modality produce a stable, repeatable bladder-related signal under realistic placement conditions?

    What this stage should settle

    • Signal-to-noise under movement and shifting contact
    • Power, thermal, and packaging constraints
    • Whether ultrasound keeps its lead or loses it
  2. Stage 02

    02

    Human factors and overnight wear

    Decision question: Can children or families tolerate the form factor long enough for repeated overnight use?

    What this stage should settle

    • Patch comfort, adhesion, and body-position drift
    • False alert burden versus missed-event burden
    • What the wristband and caregiver escalation should actually feel like
  3. Stage 03

    03

    Pilot feasibility studies

    Decision question: Does the signal hold in real nightly conditions well enough to justify a larger validation path?

    What this stage should settle

    • Threshold calibration across body variation
    • When the cue arrives relative to voiding
    • Where the concept breaks and needs redesign
  4. Stage 04

    04

    Clinical and regulatory design

    Decision question: What evidence package is actually required before discussing clinical usefulness or commercial readiness?

    What this stage should settle

    • Study endpoints and partner requirements
    • Regulatory posture for intended use
    • Commercial language that remains out of bounds

Validation roadmap

The next 90 days should reduce technical risk, not inflate the story.

DryNight becomes more credible when each stage answers a concrete proof question. The roadmap below is intentionally narrow because the company is pre-prototype and not clinically validated.

DryNight is not FDA-cleared, not clinically validated, and not available for diagnosis, treatment, or medical decision-making. The current work is feasibility, human factors, and study design.

0–30 days

Lock the product claim and evidence file

Define the first claim as pre-void cue feasibility, not bedwetting treatment.

  • Write the intended-use boundary and prohibited claims list.
  • Complete a source map for enuresis care, wetness alarms, and bladder-monitoring literature.
  • Define the minimum useful lead-time endpoint before any prototype study.

Decision gate Can the company explain exactly what it is testing without implying that the device already works?

31–60 days

Choose the first sensing experiment

Compare candidate sensing paths against the realities of overnight pediatric wear.

  • Specify ultrasound and bioimpedance bench tests, including motion and contact-loss cases.
  • Define patch placement, adhesion, comfort, power, and thermal constraints.
  • Create a failure-mode table for false cues, missed cues, skin contact loss, and parent fatigue.

Decision gate Is there a signal path worth prototyping on the body?

61–90 days

Prepare human-factors and feasibility work

Turn the technical experiment into a study-ready product program.

  • Draft a repeated-night usability protocol for comfort, adherence, and setup burden.
  • Recruit pediatric continence, wearable sensing, regulatory, and manufacturing advisors.
  • Build a funding memo tied to signal feasibility, cue lead time, and usability gates.

Decision gate Is DryNight ready for a controlled prototype build and clinician-reviewed feasibility plan?

Risks to de-risk first

The company should earn confidence one failure mode at a time.

  • 01 Overnight signal quality
  • 02 Patch placement drift
  • 03 Motion artifacts
  • 04 Sleep posture
  • 05 Skin contact and comfort
  • 06 Power and battery limits
  • 07 False alarms and missed cues
  • 08 Useful lead time before voiding
  • 09 Parent fatigue
  • 10 Pediatric safety and usability

Why ultrasound, for now

The right modality is the one that survives real use, not the one that sounds most futuristic.

Ultrasound is being explored because it could, in principle, observe bladder filling directly enough to support a pre-void cue. That still leaves the work that matters: proving the signal, proving the body interface, and proving that the alert reduces burden rather than adding a new one.

01 Why ultrasound leads today

Signal specificity

The lead method should be able to observe bladder-state changes directly enough to justify a pre-void cue. Miniaturization, coupling, motion tolerance, and power budget remain open engineering gates.

02 The practical gate

Overnight wearability

The sensor must stay positioned through sleep without making the child feel like a patient in a study. Adhesion, comfort, heat, charging, and cleaning matter as much as signal quality.

03 The clinical gate

Alert threshold

The useful output is not a stream of readings. It is a conservative decision point that can be tested against real nights, false cues, missed cues, and caregiver burden.

Evidence plan

Turn a plausible signal into an investable product.

DryNight is not another moisture alarm. The company thesis is upstream timing: detect bladder filling early enough to cue the wearer first, then escalate only when help is needed. The evidence plan reduces the three risks that matter most: signal quality, overnight wearability, and family action.

  1. 01

    Literature

    External signal

    Bladder sensing is scientifically plausible

    Peer-reviewed work has already explored noninvasive and wearable bladder monitoring, including pediatric lower-abdomen ultrasound studies. DryNight starts from that precedent, then narrows the first product question.

  2. 02

    Feasibility

    First company risk

    Prove a usable overnight signal

    The first technical milestone is to separate bladder filling from motion, coupling, body variation, and sleep-position noise while keeping the wearable comfortable enough for repeated nights.

  3. 03

    Experience

    Adoption standard

    Make the cue private enough to use

    A better signal only matters if the patch, wrist cue, setup, charging, and caregiver escalation fit real homes without adding shame or nightly burden.

  4. 04

    Validation

    Fundable milestone

    Prove the first milestone worth funding

    The strongest first milestone is focused: timely pre-void cueing before wetness starts. Broader pediatric, adult, older-adult, and care-facility use cases should follow evidence, not precede it.

The first clinical conversations should be about signal quality, comfort, family burden, and the evidence threshold required before the company expands its public product story.

Evidence room

A credible company starts with a credible proof plan.

DryNight earns attention by being precise. The evidence room explains why the idea is plausible, where the first risk sits, and what proof would move the company from concept to funded medical-device program.

Problem reality

Care reality

The first proof is not technical. The first proof is that timing, dignity, and caregiver burden matter enough to justify a better product.

  • Bedwetting is common in school-age children and often resolves gradually rather than immediately.

  • Most household alarms start when wetting begins, not when the bladder first becomes actionable.

  • Families need earlier information and less public interruption, not a louder signal after wetness has already reached clothing or bedding.

Technical precedent

Published precedent

Outside literature makes the sensing thesis serious enough to test. It does not remove the need for DryNight to prove its own hardware, software, and user experience.

  • Wearable lower-abdomen ultrasound detected full bladders before voiding in 90% of a 30-child urodynamic cohort aged 6 to 12.

  • Overnight home monitoring of natural nocturnal bladder filling was feasible in children with monosymptomatic nocturnal enuresis on 83% of monitored nights without disturbing sleep.

  • Noninvasive bladder monitoring is an active research area across ultrasound, bioimpedance, optical sensing, and flexible ultrasonic devices.

Product thesis

Company thesis

DryNight is taking a clear position: the winning product is not only a sensor. It is a private timing system that fits the home.

  • The first wedge is a soft lower-abdomen patch, a private wearer cue, and optional caregiver escalation.

    Company thesis, validation milestone

  • The first product milestone should be narrow: timely pre-void cueing before wetness starts.

    Company thesis, validation milestone

  • The same timing problem can later support adult, older-adult, and caregiver workflows once the pediatric proof point is earned.

    Company thesis, validation milestone

Validation milestones

Next proof

This is the work that turns a strong idea into an investable medical-device program.

  • Select the sensing architecture that survives body-size variation, sleep position, motion, adhesion, and power constraints.

  • Define an actionable threshold that balances missed cues, false cues, wearer comfort, and caregiver burden.

    Company thesis, validation milestone

  • Run repeated-night usability and a clinician-reviewed pilot before expanding the market story.

Investor diligence

Why is this a company, not just a feature?

The unmet need is not a cleaner wetness alarm. It is earlier, quieter, more private timing. A product that can identify a useful pre-void window has a different value proposition for families, pediatric continence care, older-adult care, and long-term caregiver workflows.

What makes the technical thesis credible?

The literature already includes noninvasive bladder monitoring, wearable ultrasound work, pediatric urodynamic testing, and overnight home monitoring in children with nocturnal enuresis. That is enough to justify serious feasibility work, especially if DryNight stays focused on a narrow first milestone.

Where is the first technical risk?

Signal quality under real overnight conditions. The system must handle motion, sleep position, body variation, sensor coupling, adhesion, battery life, and the difference between a useful trend and noise.

What would make the next financing round credible?

A credible round should be tied to specific de-risking: bench signal quality, a wearable form factor, repeated-night comfort, a defensible cue threshold, and a clinician-reviewed pilot protocol. Those milestones are concrete enough for investors, advisors, and device partners to pressure-test.

Why keep the first milestone narrow?

Because a narrow milestone can be tested, funded, and defended. Pediatric nocturnal enuresis gives DryNight a specific first wedge. Adult and older-adult continence workflows become stronger expansion paths after the signal, comfort, and cue logic are validated.

What the company needs

Clinical and study design

DryNight needs advisors who can turn the first milestone into a study plan that matters clinically and commercially.

  • 01 Pediatric urology, continence, sleep, and behavioral-health input on patient selection and meaningful endpoints
  • 02 Feedback on what counts as clinically useful pre-void notice versus noise
  • 03 Early design help for feasibility, human-factors, and pilot study protocols

Wearable sensing and manufacturing

The hardware path has to be comfortable, low-power, manufacturable, and strong enough for repeated overnight wear.

  • 01 Wearable ultrasound, bioimpedance, signal processing, low-power electronics, and patch mechanics expertise
  • 02 Advice on coupling, motion artifacts, overnight adhesion, battery tradeoffs, and manufacturable form factors
  • 03 Reality checks on whether a pediatric overnight product can be comfortable enough for repeated use

Capital and commercialization

The business path should finance the right proof, protect the first milestone, and keep the broader market in view.

  • 01 Regulatory guidance on intended use, performance language, and the right sequence of risk-reduction work
  • 02 Quality-system and manufacturing advice appropriate for an early medical-device program
  • 03 Investors and operators who fund evidence milestones, not vanity waitlist metrics

Foundational citations

Contact

Help shape the product before claims are made.

DryNight needs grounded input from families, clinicians, engineers, care operators, and investors before the company turns the concept into a device. Use this form for feedback, research conversations, partnership ideas, manufacturing leads, or funding conversations.

Best-fit outreach right now: families with lived experience, pediatric continence clinicians, research partners, wearable sensing engineers, regulatory operators, manufacturing partners, and investors who care about feasibility discipline more than early polish.

What happens next

01

Route the note

We use your role and interest to separate family feedback, clinical conversations, manufacturing leads, and investor outreach.

02

Follow up only when relevant

The goal is a useful conversation, not a mailing list.

03

Keep the conversation useful

DryNight is not collecting medical advice requests or private patient details through this form.

Submissions go to the DryNight team through Formspree.

Please do not include urgent medical questions, protected health information, or private details about a child or patient. This form is for product feedback, partnerships, and general contact.

Powered by Formspree. Exportable later to Sheets, Notion, Airtable, HubSpot, or webhooks.