SmartSurf and local conditions
Building around water sports made the limits of location alone tangible: operators need environmental context, and any source can be stale, distant or unrepresentative.
Investor brief · November 2026
Wind evidence for drone software teams to review.
Senlay brings available wind observations and forecasts for a selected coordinate into a structured response, with source, timestamp, distance, disagreement and missing evidence visible.
The first buyer hypothesis is a team building software for drone operators. The workflow, demand and repeatable field value have not yet been validated. Senlay is an evaluation beta; it does not assess whole-mission suitability, authorize launch or control a robot.
Origin and sequence
SmartSurf revealed the need. Robotics is the first market hypothesis to test.
SmartSurf is the founder's origin story and an existing prototype/reference application in maritime conditions. It is not proof of robotics demand or validated safety outcomes.
Wind evidence at a point
Senlay structures available measurements and forecasts with provenance, time, distance, source agreement, coverage and unknowns for human or software review.
Drone software teams
Test whether this evidence fits an operator or integration engineer's review workflow. Customer demand and field utility are not yet established.
Scoped pilot, if evaluation supports it
Define a field protocol, sources, operating context, success measures and commercial/source rights with a prospective partner before calling it validated.
One workflow
Make the evidence inspectable before an operator makes a decision.
The current drone assessment profile checks wind speed, gust and direction evidence. It does not evaluate aircraft-specific limits, route, altitude, obstacles, visibility, airspace permission or mission suitability.
Select a coordinate
A developer requests the available wind evidence for a place and time through the API or reference adapter.
Inspect sources and gaps
Review observation versus forecast, source and timestamp, age and distance when available, coverage, disagreement and unknowns.
Keep mission authority outside Senlay
The operator's application and established procedures make any operational decision. Senlay does not provide launch clearance.
Evaluation example: request wind evidence for a selected coordinate, then inspect which measurements and forecasts are available, how old and distant they are, whether they disagree, and what the response cannot establish.
Business hypothesis
Prove a repeatable workflow before sizing a commercial model.
Self-serve evaluation is available subject to published limits and provider terms. Paid subscriptions are planned and unlaunched. Commercial source rights, production reliability and willingness to pay remain open questions.
Drone software teams
Hypothesis: teams may value a structured, source-aware wind response in operator review or integration workflows. No paid robotics customers or validated external outcomes are claimed.
Agree a scoped test
Discuss the target workflow, allowed source rights, test locations, evidence requirements and evaluation measures. Commercial terms follow only if the scope and rights are agreed.
Milestones · dated 1 November 2026
Separate shipped capability from evidence still to earn.
These are sequencing priorities, not dated delivery commitments or financing terms.
| Stage | Evidence and work |
|---|---|
| Available now | Spot-level environmental API; source-aware wind observations and model values where available; timestamps, distance, conflicts and unknowns; deterministic snapshot summary; REST/API, public MCP gateway, reference adapters and synthetic replay. |
| Evaluate next | Interview and test with drone software teams; define one operator-review workflow; measure usefulness, source representativeness and integration effort without assuming positive results. |
| Validate in a scoped pilot | Only after a partner, protocol, location and source rights are agreed: assess field behavior, repeatability, reliability and willingness to pay. Real hardware validation remains pending. |
| Later, if justified | Consider mission route/time-window evaluation or broader verticals only after the point-level workflow and customer need are demonstrated. |
Founder and origin
Built from SmartSurf and hands-on work in wind and water.
Founder Viktor Kryvotsiuk's experience with water-sports instruction and SmartSurf prototyping led to the question behind Senlay: how can an application show the environmental evidence available for a particular place?
Pre-revenue; external validation remains open
No paid robotics customers, field validation or measured customer outcomes are represented here. SmartSurf is product origin/reference experience, not commercial proof for this robotics hypothesis.
Evaluate one workflow.
Try the current wind evidence demo or discuss a scoped robotics evaluation. The evaluation should test whether the available evidence helps the intended user; it should not treat a complete response as mission clearance.