Celebrace software is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include orthodontic devices (orthodontic wires, orthodontic brackets and bonding trays). To use Celebrace Software, users must have the necessary education and domain knowledge in orthodontic practice and receive dedicated training in the use of the software.
Device Story
Software-only device for orthodontic treatment planning; inputs include intraoral scans, CBCT radiographs, and patient demographics. Transforms inputs into treatment plans and design files for orthodontic wires, brackets, and bonding trays. Used by dental professionals in clinical settings; requires specialized orthodontic education and training. Output reviewed and approved by treating dentist to guide clinical decision-making and physical manufacturing of devices. Benefits include optimized treatment planning and customized orthodontic device design.
Clinical Evidence
Bench testing only. Software verification and validation performed per FDA guidance and ANSI/AAMI/IEC 62304 standards. No clinical data presented.
Technological Characteristics
Software-only device; static, locked algorithm. Inputs: intraoral scans, CBCT, demographics. Outputs: 2D/3D treatment plans and design files for orthodontic hardware. Does not perform tooth segmentation (relies on external cleared software). Operates on standard IT hardware/OS environments.
Indications for Use
Indicated for dental professionals to assist in orthodontic treatment planning and design of orthodontic devices (wires, brackets, bonding trays) based on patient images and 3D mesh data.
Regulatory Classification
Identification
An orthodontic plastic bracket is a plastic device intended to be bonded to a tooth to apply pressure to a tooth from a flexible orthodontic wire to alter its position.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
December 29, 2025
Celebrace
Sarah Moss
Regulatory Affairs Consultant
5708 Colleyville Blvd., Suite A
Colleyville, Texas 76034
Re: K253343
Trade/Device Name: Celebrace Software
Regulation Number: 21 CFR 872.5470
Regulation Name: Orthodontic Plastic Bracket
Regulatory Class: Class II
Product Code: PNN
Dated: September 19, 2025
Received: September 30, 2025
Dear Sarah Moss:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K253343 - Sarah Moss
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K253343 - Sarah Moss
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
MICHAEL E. ADJODHA -S
Michael E. Adjodha, MChE, RAC, CQIA
Assistant Director
DHT1B: Division of Dental and ENT Devices
OHT1: Office of Ophthalmic, Anesthesia, Respiratory, ENT, and Dental Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740
EF
| DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration Indications for Use | Form Approved: OMB No. 0910-0120 Expiration Date: 07/31/2026 See PRA Statement below. |
| --- | --- |
| 510(k) Number (if known) K253343 | |
| Device Name Celebrace Software | |
| Indications for Use (Describe) Celebrace software is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include orthodontic devices (orthodontic wires, orthodontic brackets and bonding trays). | |
| To use Celebrace Software, users must have the necessary education and domain knowledge in orthodontic practice and receive dedicated training in the use of the software. | |
| Type of Use (Select one or both, as applicable) ☑ Prescription Use (Part 21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | |
| CONTINUE ON A SEPARATE PAGE IF NEEDED. | |
| This section applies only to requirements of the Paperwork Reduction Act of 1995. *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.* | |
| The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to: Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov | |
| "An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number." | |
{4}
| 510(k) #: K253343 | 510(k) Summary | Prepared on: 2025-12-29 |
| --- | --- | --- |
| Contact Details | | 21 CFR 807.92(a)(1) |
| Applicant Name | Celebrace | |
| Applicant Address | 5708 Colleyville Blvd., Suite A Colleyville TX 76034 United States | |
| Applicant Contact Telephone | 281-795-1812 | |
| Applicant Contact | Ms. Sarah Moss | |
| Applicant Contact Email | smoss@primepathmedtech.com | |
| Device Name | | 21 CFR 807.92(a)(2) |
| Device Trade Name | Celebrace Software | |
| Common Name | Orthodontic plastic bracket | |
| Classification Name | Orthodontic Software | |
| Regulation Number | 872.5470 | |
| Product Code(s) | PNN | |
| Legally Marketed Predicate Devices | | 21 CFR 807.92(a)(3) |
| Predicate # | Predicate Trade Name (Primary Predicate is listed first) | Product Code |
| K233625 | Raydent Software | PNN |
| K232429 | Titan Dental Design | PNN |
| K203442 | Inbrace Orthodontic Syste | PNN |
| Device Description Summary | | 21 CFR 807.92(a)(4) |
| Celebrace software is a software only device that creates an orthodontic treatment plan. The input to Celebrace Software are a combination of Intraoral Scans, CBCT radiographs and patient demographics. The output of the Celebrace Software is a treatment plan, which is approved by the treating dentist, and files used for physical manufacturing of the orthodontic devices (orthodontic wires, brackets and bonding tray). The software is powered by a static algorithm that is locked at the time of release. | | |
| Intended Use/Indications for Use | | 21 CFR 807.92(a)(5) |
| Celebrace software is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include orthodontic devices (orthodontic wires, orthodontic brackets and bonding trays). | | |
| To use Celebrace Software, users must have the necessary education and domain knowledge in orthodontic practice and receive dedicated training in the use of the software. | | |
| Indications for Use Comparison | | 21 CFR 807.92(a)(5) |
{5}
Celebrace software system outputs treatment device designs for orthodontic wires, brackets and indirect bonding trays. The predicate device outputs treatment device designs for prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner). The reference device output treatment device designs for bonding trays and clear aligners. The subject device creates 2D and 3D outputs, while the predicate device and reference device only output 3D designs.
## Technological Comparison
21 CFR 807.92(a)(6)
Based on the above comparisons, the design, construction, and performance characteristics of the Subject Device are similar to that of the Predicate Devices.
The differences identified are not substantial differences in operation of the device.
Technological Features: Celebrace software system does not design prosthetics. This difference does not impact the efficacy of the software.
Analysis Features: Celebrace software system does not perform tooth segmentation. The segmentation of the teeth is done using a 510(k) cleared segmentation software (K233925). This difference does not impact the efficacy of the software and does not introduce any new risks.
OS/Hardware/IT Requirements: The differences between the predicate and subject device account for differences in the operating environment, but do not impact the intended use or application of the devices.
There are no other substantial differences between the technical requirements between the Subject and Predicate Devices.
## Non-Clinical and/or Clinical Tests Summary & Conclusions
21 CFR 807.92(b)
The Subject Device has passed testing for appropriate verification and validation and performed per its intended use.
Software documentation was prepared per the recommendations of FDA Guidance Document, "Content of Premarket Submissions for Device Software Functions (Issued on June 14, 2023)," and ANSI/AAMI/IEC 62304: Medical Device Software - Software life cycle processes.
Based on the performance testing and software validation testing, the Subject Device, Celebrace Software, has been shown to be appropriate for its indications for use and is as safe and as effective as the legally marketed Predicate Device, Raydent SW (K233625). There are no substantial differences between the indications for use, technological features, or performance testing of the Subject and Predicate Device.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.