Objects

Everything in a building is a real thing before it is a drawing of a thing. A door is a door, with a swing, a frame, a fire rating, and a relationship to the wall it lives in, not a symbol standing in for one. Corvus is built object-first. Every element you place has its own identity and intelligence, stays connected everywhere it is used, and updates consistently wherever it appears. This is the foundation for everything else: drawings, models, libraries, worksheets, BIM, and documentation.

Work with things, not representations of things.

A wall should not become one thing in a model, another in a drawing, and a collection of disconnected information somewhere else. In Corvus, an object remains the same object wherever you encounter it. Its geometry, properties, relationships, and representations belong together, so you can work with the architecture rather than manage separate versions of it.

Start with what you know.

A door can begin as a door. A chair can begin as a chair. You should not have to define every parameter, specification, or future decision before placing something in a project. Corvus lets objects begin with exactly as much information as you know and gain specificity as the design develops.

Let objects grow with the project.

Design decisions happen over time. A generic window may later gain exact dimensions, materials, performance requirements, manufacturer information, and a product number. Corvus lets the object become more specific without becoming a different thing. The information grows with the project instead of getting in the way of it.

Make objects smarter without making models heavier.

Intelligent objects should make the work easier, not the model slower. Corvus gives objects the information and behavior they need without burdening them with unnecessary geometry, excessive parameters, or layers of hidden complexity. Intelligence stays useful, objects stay lightweight, and projects stay responsive as they grow.

See the same object correctly in every view.

The same door appears in plan, elevation, section, perspective, detail, and schedule, but each representation needs to communicate something different. Corvus understands those representations as views of the same object. You do not have to construct separate 2D and 3D versions and continually keep them aligned.

Show the right information at every scale.

A building element should communicate appropriately whether you are looking at a broad plan or a detailed drawing. Corvus lets objects respond to drawing scale and context while preserving the identity underneath. You see the information appropriate to the work at hand without turning one architectural element into a collection of unrelated graphics.

Keep every object connected to what surrounds it.

A door lives in a wall. A window creates an opening. A fixture belongs in a room. A stair connects levels. Buildings are systems of things that relate to other things, and Corvus understands those relationships directly. Change one part of the system and the connected parts can respond without forcing you to reconstruct those relationships by hand.

Change an object once and update it everywhere.

Place an object once or use it hundreds of times. Its identity stays intact. When you change the source object, Corvus can carry that change everywhere it is used while preserving the differences that make individual instances unique. You spend less time hunting through a project for copies and more time making the change itself.

Create the objects your work actually needs.

Objects should not force you into someone else's assumptions. Create what you need, modify what you have, or bring something in and make it useful. Corvus keeps the process direct so creating a custom architectural object does not become a separate technical discipline.

Build intelligent objects without becoming a programmer.

Creating a useful object should not require scripts, elaborate formulas, nested containers, or specialist knowledge. Corvus puts the underlying intelligence in the system itself. Define the thing, give it the properties and behaviors that matter, and get back to designing.

Bring in useful objects without bringing in the baggage.

Downloaded objects often arrive with far more than you asked for: excessive geometry, irrelevant metadata, locked properties, inconsistent naming, and unnecessary complexity. Corvus helps you bring useful objects into your work without inheriting all of their baggage. Keep what matters. Leave behind what doesn't.

Keep information with the object it describes.

Dimensions, materials, finishes, ratings, costs, manufacturers, product numbers, and other properties are not miscellaneous data attached somewhere nearby. They describe the object. Corvus keeps that information with the thing it belongs to, making it available wherever the project needs it.

Let object information flow through the entire project.

Object information should not have to be recreated for every drawing, schedule, worksheet, or deliverable. Because Corvus maintains a common underlying object, its information can flow throughout the project. Edit the object, the drawing, or the worksheet and you are working with the same connected information.

Turn every good object into a reusable studio asset.

A good object should become an asset. Save the door, fixture, furniture piece, assembly, material, or detail you created and it becomes part of your library, ready for the next room, the next project, or the entire studio. The work you do today makes tomorrow's work faster.

Keep your library useful as it grows.

Libraries accumulate duplicates, outdated versions, mystery objects, and slightly different copies of the same thing. Corvus gives objects persistent identity, making them easier to organize, find, update, and reuse. Your library becomes a living collection of trusted studio knowledge instead of a folder you are afraid to clean up.

Carry every change all the way to documentation.

Because drawings, models, worksheets, and documentation all refer to the same underlying objects, information does not have to be repeatedly translated from one representation into another. A change can move through the project instead of becoming another coordination task. What you design and what you document stay connected.

Get BIM intelligence without the BIM busywork.

Objects already know what they are, what information they carry, and how they relate to the things around them. That means much of the intelligence traditionally associated with BIM can happen naturally as you work. You design the building. Corvus maintains the underlying structure.

Spend your time designing the building, not managing the software.

Architecture already gives us the organizing logic: walls, doors, windows, rooms, materials, fixtures, assemblies, and the relationships between them. Corvus starts there. You work with recognizable architectural things while the system manages the complexity underneath. The software gets out of the way, and the building stays at the center.

Join our waitlist.

You’ve already waited 49 years. What’s another two? AEC professionals have spent decades jumping through hoops and creating workarounds for convoluted software. No one dares to build something that will challenge the status quo. It's time for something fundamentally different and unapologetically human. Join the waitlist.