Camera Roll
Hundreds of photos without cycle context.
Private grow memory · Closed beta
Remember every grow. Improve every cycle.
Capture. Compare. Learn. Carry forward.
Cambris brings photos, notes, checkpoints, tasks, issues, and outcomes together—so you can see what changed and preserve what matters for the next cycle.
- Private by default
- iPhone, iPad, and web
- Works with existing gear
PEPPER TENTFRUITING
PhotoWaterNoteIssue
Checkpoint compareFront canopy
AVAILABLE
DAY 26DAY 68Checkpoint coverage improved61% → 82% in this fictional cycle
Two issues resolvedActions and follow-ups preserved
The fragmented-grow problem
Your grow history already exists. It is just not together.
Photos live in Camera Roll. Conditions live in controller charts. Notes, reminders, decisions, and outcomes end up somewhere else—or stay in memory until the details fade.
Notes
Observations without the matching evidence.
Controller charts
Conditions separated from actions and outcomes.
Reminders
Work gets done, but rarely becomes reusable memory.
Messages
Advice and decisions scattered across conversations.
One cycle. One timeline. One place to learn from what happened.
The Cambris loop
Capture. Compare. Learn. Carry forward.
The product is designed around a simple loop that becomes more valuable with every completed cycle.
Capture what happened.
Save photos, notes, watering, feeding, work actions, issues, harvests, and readings without turning the grow into paperwork.
See change clearly.
Use named checkpoints, reference angles, and date-to-date comparison instead of searching an unstructured camera roll.
Connect actions to outcomes.
Keep issues, suspected causes, interventions, follow-ups, and results together in the context where they happened.
Make the next cycle better.
Close the grow, record what worked, and preserve the notes and learnings worth returning to next time.
Product proof
A useful grow record should not feel like homework.
Fast daily logging
Capture the evidence now. Add detail only when it helps later.
Cambris starts with the current space, cycle, stage, date, and time so common logs stay fast. If you are interrupted, the in-progress draft is preserved locally.
- Photo and note without a long form
- One-tap water, feed, prune, and harvest logs
- Calm confirmation instead of blocking flows
Coming soonRecall recent amounts and recipes while logging.
Quick logWhat happened?
Available01Photo02Note03Water04Feed05Prune06Harvest07Issue08Journal
Draft protectedYour unfinished entry stays on this device if you are interrupted.
Repeatable visual memory
Stop guessing which photo matches which week.
Name the views that matter—front canopy, side structure, fruit close-up, underside inspection—and capture them on a repeatable rhythm. Compare the latest view with its reference.
- Reference image and capture instruction
- Split and overlay comparison modes
- Observation prompt after comparison
Coming soonCreate an issue directly from a visual change.
Front canopyDay 26 → Day 68
AvailableFictional demonstration image · fixed-angle checkpoint
Issues and follow-up
Turn problems into trackable experiments.
Record the issue, suspected cause, action taken, and follow-up. Keep the evidence and outcome attached so the result does not disappear into memory.
- Severity and suspected cause
- Actions and supporting photos
- Resolution notes and follow-up reminders
Issue recordLower leaf curl
Available01ObservedLower leaves curling inward
02Suspected causeLow airflow beneath canopy
03ActionAdjusted fan and pruned
04Follow-upImproved after three days
Review and compare
The end of the grow should improve the next one.
Review the completed cycle, compare it with an earlier run, capture outcomes, and leave clear carry-forward notes for the grower you will be next time.
- Compare completed cycles side by side
- Capture outcomes and closeout rating
- Preserve carry-forward notes
Coming soonReuse selected tasks and checkpoints in a new cycle.
Cycle compareWinter run vs. Spring run
AvailableWinter run87 days24 checkpoints · 3 issues
Spring run92 days31 checkpoints · 2 issues
Outcome note
More consistent checkpoint coverage made the later-cycle changes easier to review.
See the payoff
Explore a grow report, not just a feature list.
The fictional Sugar Rush Peach Stripey report shows checkpoint comparison, issue follow-up, environment context, timeline highlights, and close-cycle reflection through the same structure used by private shares.
All names, dates, measurements, events, and visuals in the report are fictional and illustrative. Timelapse remains clearly labeled as coming soon.
Product preview
FictionalSugar Rush Peach Stripey
Pepper Tent · Completed cycle
92dDuration
31Checkpoints
2Issues resolved
84%Tasks completed
BetaThe demo and private share viewer now use the same versioned report contract.
Private by default
Your grow stays private until you decide otherwise.
Cambris is designed as a private operating memory, not a public feed. A report is created only when you choose a scope and generate a read-only link.
Private by default
Nothing becomes public just because it was logged.
Scoped reports
Choose a weekly summary, issue case, cycle snapshot, or full-cycle scope.
Revocable access
Expire or revoke a link without deleting the underlying grow.
No recipient account
A trusted reviewer can open a read-only report in a browser.
Draft protection
In-progress entries are preserved locally if you are interrupted.
Existing gear
Cambris complements controller and camera ecosystems instead of replacing them.
Closed beta
Help shape Cambris through a real grow cycle.
Applications are open for a small group of indoor growers who can use Cambris in real conditions, tell us where it helps, and show us where it gets in the way.
Apply for closed beta- 01Free closed-beta accessNo paid subscription or automatic conversion.
- 02Direct feedback channelsShort, honest feedback is more useful than perfect usage.
- 03Private participationNo public sharing requirement and no social feed.
- 04Your existing setupUse any controller ecosystem—or none at all.
Frequently asked
Clear boundaries from the start.
Is Cambris a grow controller?
No. Cambris is the memory, review, and learning layer around the grow. It is not intended to replace controller apps or operate grow hardware.
Is Cambris only for cannabis?
No. Cambris is crop-agnostic and is being built for peppers, tomatoes, herbs, ornamentals, cannabis-friendly users, and other indoor growing workflows.
Do I need special hardware?
No. The core app does not require proprietary hardware. Optional automated still-image capture is in development for a later beta cohort.
Will my grow be public?
No. Cambris is private by default. Sharing requires an explicit report action, and a recipient sees only the content included in that report.
Does Cambris work fully offline?
Not yet. In-progress drafts are preserved locally if you are interrupted, while cloud mutations and media uploads currently require connectivity.
Is the closed beta paid?
No. Closed-beta access is free, time-bounded, and will not silently convert into a paid subscription.