About DEEVLA

Building workflow technology around real Maya production needs.

DEEVLA is an independent DCC technology initiative focused on improving digital content creation workflows. Its first product, DEEVLA Asset Browser (DAB), is being developed as a high-performance asset and workflow infrastructure for Autodesk Maya. Beyond DAB, DEEVLA's product direction includes artist tools, plugins, workflow automation, and a deeply integrated Maya-native IDE for tool and pipeline development.

Explore DAB

Current Focus

  • DEEVLA Asset Browser (DAB) as the first product
  • Autodesk Maya desktop integration
  • Production-oriented workflow design
  • Architecture, scalability, and maintainability

Long-Term Direction

  • DEEVLA Smart Modeling Toolkit
  • Additional Maya tools and plugins
  • Workflow automation and pipeline utilities
  • DEEVLA IDE — native-feeling development inside Maya
Company / Initiative

Independent development, built around real Maya production needs.

DEEVLA began as an independent effort to explore better ways of working inside modern DCC environments. The first DAB concept and early prototypes began in 2025. More focused and structured development began in August 2026 as DAB became the first product under the DEEVLA initiative.

Founded / Structured Development
August 2026
DAB Early Prototyping
2025
Team Size
1 — Founder
Employees
0
Location
Indonesia
Current Status
Early-stage R&D
Primary Autodesk Product
Autodesk Maya
Development Focus
Desktop Integration
Official Startup / Incubator Program
No — Independent / Founder-Led
Primary Development Site
Surabaya, East Java, Indonesia

DEEVLA is currently developed by its founder as an independent project. Certain visual assets, such as selected icons, may receive occasional voluntary creative contributions from external collaborators. These contributors are not employees or members of the DEEVLA development team.

Startup / Incubator Status: No. DEEVLA is not currently part of an official startup, incubator, accelerator, university, or sponsored development program. DEEVLA is a founder-led, independent development initiative.
DEEVLA is an independent initiative. No official partnership with Autodesk is claimed.
Team & Growth Direction

Founder-led today, structured to grow responsibly.

DEEVLA is currently a founder-led independent development initiative, with Riyadus Solihin serving as its founding developer and the primary person responsible for product direction, research, workflow design, prototyping, development, and validation.

Current Structure

Single independent core

At this early stage, DEEVLA is intentionally kept small and focused so its core technology, product architecture, engineering standards, and long-term direction can be established carefully before the team expands.

Current Team

Founder-led development

Current Team: 1 founder. Employees: 0. Selected visual assets may receive occasional voluntary creative contributions from external collaborators, but those contributors are not employees or members of the DEEVLA development team.

Growth Model

Gradual, product-driven expansion

Team growth is intended to follow real product and engineering needs rather than expanding prematurely. The goal is to keep development focused, maintainable, and technically disciplined.

Future Roles

As DEEVLA products mature and the development scope grows, the initiative may recruit software developers, technical artists, UI/UX specialists, pipeline engineers, QA/testing specialists, and other professionals whose expertise matches the requirements of future products.

Long-Term Team Objective

The long-term objective is to build a capable professional development team that can create reliable, production-oriented tools, plugins, workflow technologies, and developer solutions for Autodesk Maya users and modern DCC production workflows.

DEEVLA is currently being built from a single independent core. The intention is not to remain permanently as a one-person project, but to establish a strong technical and product foundation first. As the initiative grows, DEEVLA aims to evolve into a professional development team capable of supporting multiple Autodesk Maya products and long-term DCC technology development.

Growth principle: Future expansion will be approached gradually, with emphasis on technical quality, maintainability, user needs, responsible software development, and compliance with Autodesk development and licensing requirements. DEEVLA does not currently claim any official partnership or affiliation with Autodesk.
Phase 1 — First Product

DEEVLA Asset Browser (DAB)

DEEVLA Asset Browser is the first product being developed by DEEVLA for Autodesk Maya. DAB is not intended to be only a thumbnail browser. It is being designed as an asset and workflow layer that helps artists and technical users organize, discover, inspect, manage, and use production assets efficiently while minimizing interruptions to Maya's creative workflow.

How DAB Works with Autodesk Maya: DAB is a desktop-integrated Maya product. Its planned workflow uses supported Maya scripting and API mechanisms for scene-aware asset operations such as import, open, reference, selection/context handling, callbacks, and host integration. Asset indexing, metadata, thumbnails, caching, and other suitable heavy operations are designed to run through background processing so Maya's UI and viewport remain responsive.
Core Objective

High-performance asset infrastructure

DAB targets large asset libraries, fast discovery, persistent metadata, background processing, scalable indexing, and responsive interaction inside a Maya-centered workflow.

Maya Integration

Direct workflow connection

Planned Maya workflows include import, open, reference, scene-context awareness, Maya commands, and supported scripting/API integration.

Artist Experience

Less interruption, more creative focus

Expensive operations such as indexing, thumbnail generation, metadata extraction, and dependency analysis are intended to run through background job systems where appropriate.

First Product In Development Autodesk Maya 2026+ Maya 2027.2 Primary Validation Host Desktop Workflow
Phase 1 Capability Direction

Designed to become more than a traditional asset browser.

The following areas represent the planned capability direction for DAB. Features are being developed incrementally; items listed here describe the product roadmap and technical direction rather than claiming that every capability is already complete.

Asset Library & Indexing

  • Local asset library registration
  • Automatic asset discovery
  • Fast and incremental indexing
  • Folder and collection organization
  • Large-library scalability
  • SQLite-backed asset index and state
  • Missing or moved asset detection
  • Background scanning and indexing

Search, Filter & Discovery

  • Instant search
  • Multi-criteria filtering
  • Sorting by asset information
  • Tags
  • Favorites
  • Ratings
  • Collections and recently used assets
  • Future AI-assisted search and classification

Asset Management

  • Rename
  • Move
  • Duplicate
  • Managed Trash
  • Restore
  • Folder management
  • Batch operations
  • Asset-state tracking

Visual Browsing & Preview

  • Thumbnail generation
  • Thumbnail cache
  • Large thumbnail libraries
  • Preview information
  • Asset-type visualization
  • Background thumbnail processing
  • Future interactive 3D preview

Autodesk Maya Integration

  • Direct asset import into Maya
  • Open asset workflows
  • Reference asset workflows
  • Maya-aware asset operations
  • Scene-context integration
  • Drag-and-drop where appropriate
  • Maya scripting and API integration
  • Direct interaction with the Maya runtime

Metadata & Production Information

  • Custom metadata
  • Asset type and file information
  • Creation and modification information
  • Tags and ratings
  • Production notes
  • Technical metadata
  • Future extensible metadata providers

Dependency Intelligence

  • Dependency viewer direction
  • Texture and related-file inspection
  • Missing dependency detection
  • Related-file discovery
  • Future pipeline dependency analysis

Duplicate & Library Maintenance

  • Duplicate asset detection
  • Library cleanup tools
  • Missing-file detection
  • Orphaned metadata handling
  • Asset integrity checks

Texture, Material & HDRI Workflows

  • Texture-oriented asset browsing
  • Material organization
  • HDRI library management
  • Future texture/material utilities
  • Batch processing and conversion direction

Modern Pipeline Interoperability

  • OpenUSD-oriented workflows
  • MaterialX-oriented workflows
  • Extensible import/export architecture
  • Provider-based format support
  • Modern DCC pipeline interoperability

High-Performance Architecture

  • Background processing
  • Job queue / worker system
  • Non-blocking UI direction
  • Minimal Maya UI and viewport interruption
  • Caching
  • Incremental indexing
  • Efficient persistent database
  • Native components only where justified

Sync, Extensibility & Intelligence

  • Planned P2P / Hybrid Sync
  • Shared-library direction
  • Modular service/provider contracts
  • Third-party extension direction
  • AI-assisted tagging and semantic discovery
  • Workflow recommendations
Technology Stack & Engineering Approach

Built as a multi-language, production-oriented Maya product.

DAB is intentionally not built around a single programming language. The planned architecture uses different technologies for the jobs they are best suited to. Python provides direct, flexible integration with Autodesk Maya and rapid extension of artist workflows, while C++ is reserved for performance-sensitive native core operations where throughput, memory efficiency, and low overhead matter. The two layers are connected through a controlled binding layer so DAB can remain both fast and maintainable.

Technology Role in DAB Why it is used
Python Maya host integration, application orchestration, commands, extensibility, services, and workflow logic. Python is deeply established in Maya pipelines, allows rapid development, and keeps artist/pipeline extensions accessible.
PySide6 / Qt6 Dockable Maya UI, library views, asset grids, search/filter controls, metadata panels, settings, and user interaction. Provides a modern Qt interface that can integrate naturally with supported Maya desktop workflows.
Modern C++ Performance-critical native core operations such as heavy scanning/indexing workloads, hashing, cache processing, and other compute-heavy tasks where profiling justifies native code. Keeps expensive operations fast while avoiding the cost and complexity of moving the entire application into C++.
pybind11 Controlled bridge between the C++ native core and Python application / Maya integration layer. Allows a small, focused native surface instead of a large custom C++ wrapper architecture.
SQLite Local asset index, metadata, tags, ratings, collections, search state, and migration-managed persistence. Reliable embedded persistence without requiring a separate database server for normal desktop use.
Maya Python / OpenMaya APIs Scene context, selection, events, import/open/reference operations, callbacks, host capabilities, and Maya-aware actions. Provides direct integration with the Maya runtime instead of treating Maya as only an external file target.
OpenUSD / MaterialX Planned interoperability direction for modern scene, asset, and material workflows. Supports a more open and pipeline-friendly future rather than locking the asset system to a single proprietary representation.

Layered Architecture

Maya host integration, UI, services, core systems, native acceleration, persistence, and asset providers are separated to keep responsibilities clear and reduce tightly coupled code.

Background-first Heavy Work

Scanning, indexing, thumbnail generation, metadata extraction, duplicate detection, and other expensive operations are designed to use job/worker systems where safe so Maya remains responsive.

Native Only Where It Matters

C++ is used selectively for measured performance needs. DAB avoids creating a large native wrapper when Python can provide the same function cleanly and maintainably.

Version-aware Maya Integration

The target is one maintainable codebase for Maya 2026 and later, with a host/compatibility layer and capability detection rather than scattered version checks or separate forks.

Extensible Providers & Contracts

Search, metadata, preview, formats, pipeline integration, and future studio extensions are planned around explicit service/provider contracts so capabilities can grow without rebuilding the core.

Production Engineering Discipline

The direction includes versioned data migrations, regression testing, error recovery, dependency and license review, performance measurement, and packaging designed for commercial distribution.

Engineering objective: DAB is being designed using production-grade software engineering practices commonly used in professional tools and pipeline development: modular boundaries, explicit contracts, measured native acceleration, persistent data migrations, background processing, compatibility isolation, testing, and maintainable extension points.

DAB Workflow

From asset source to Maya scene — with indexing, metadata, cache, and validation handled behind the scenes.

DAB is intended to provide a simple artist-facing workflow while a structured data and background-processing layer keeps the asset library searchable, current, and ready for Maya. The workflow below represents the planned product direction and does not imply that every capability is already complete.

Register Library
Discover & Scan
Index & Persist
Enrich & Cache
Search & Browse
Inspect & Validate
Use in Maya

Detailed Asset Flow

01

Register Asset Sources

The user adds one or more local or supported shared asset locations. DAB records the library configuration, root paths, availability, and basic source state without changing the original production files.

02

Discover & Incrementally Scan

DAB discovers supported files and folders, detects new, changed, moved, or missing items, and avoids a full rescan when only part of the library has changed.

03

Build the Searchable Index

Asset identity, path information, type, timestamps, library relationship, and other core state are written into the local persistent index so assets can be found without repeatedly walking the file system.

04

Extract Metadata & Build Cache

Suitable background jobs can generate thumbnails, extract metadata, update cache entries, inspect related files, and prepare additional information without unnecessarily blocking Maya's main UI thread.

05

Search, Filter & Organize

Artists browse visually or narrow large libraries using search, filters, sorting, tags, favorites, ratings, collections, and other discovery tools planned for the DAB library experience.

06

Preview, Inspect & Validate

Before use, the artist can inspect asset information, preview data, technical metadata, availability, dependency status, and other relevant warnings or context where supported.

07

Choose a Maya-Aware Action

DAB determines the appropriate supported workflow for the selected asset and Maya context, such as Import, Reference, Open, or another registered action exposed through the Maya integration layer.

08

Execute in Maya & Reconcile State

The selected operation is executed through supported Maya scripting/API mechanisms. DAB can then refresh relevant usage, recent-item, library, or asset state so the browser remains synchronized with the workflow.

Three Layers Working Together

Artist-Facing Layer

Browse → Search → Filter → Preview → Inspect → choose an action. The goal is to keep everyday interaction direct and understandable rather than exposing internal indexing complexity to the artist.

Background Data Layer

Scan → incremental index → metadata → thumbnails → cache → dependency/duplicate analysis. Suitable heavy operations are intended to run through queued background work while preserving Maya responsiveness.

Maya Integration Layer

Scene context → host capability checks → supported Maya command/API action → import/reference/open → state reconciliation. Maya remains the primary DCC host rather than being treated as only a file destination.

Background Processing Direction: indexing, thumbnail generation, metadata extraction, dependency analysis, duplicate detection, cache updates, and suitable batch processing are planned to use background job systems where appropriate to minimize blocking of Maya's UI and viewport. Operations that must interact with Maya's main thread will remain isolated through the host integration layer rather than being executed unsafely from workers.
Autodesk Maya Integration

Maya is the primary host application for DAB.

DAB is currently focused on direct desktop integration with Maya. The initial technical direction uses Python and Maya-supported scripting/API interfaces. Native components may be introduced only where performance-critical operations justify them, while keeping the integration architecture modular and maintainable.

Host Adapter Layer

Maya-specific commands, callbacks, host detection, scene context, and compatibility behavior are separated from DAB's core services to avoid scattering host-version logic throughout the application.

Single Codebase Direction

DAB targets Maya 2026 and later using capability detection and a compatibility layer rather than maintaining separate source forks for every Maya version.

Python-first Integration

The development approach is Python-first for Maya integration and extensibility, with native code reserved for operations that genuinely benefit from lower-level performance.

Technical Architecture

Planned core architecture.

The architecture separates Maya integration, UI, services, core systems, background processing, data persistence, and asset sources so that DAB can grow without tightly coupling every subsystem.

DEEVLA Asset Browser planned core architecture diagram Click to Zoom
Planned technical architecture. This diagram describes the intended system structure and development direction.
Planned Expansion

Future extension architecture.

DAB is being structured around service/provider contracts so that future capabilities can be added without rebuilding the entire core application.

DEEVLA Asset Browser future extension architecture diagram Click to Zoom
Planned expansion areas include OpenUSD / MaterialX, P2P / Hybrid Synchronization, AI-assisted intelligence, interactive 3D preview, third-party providers, and studio/pipeline extensions.
DEEVLA Product Roadmap

DAB first. Tools and plugins next. DEEVLA IDE as the long-term platform vision.

PHASE 1

DEEVLA Asset Browser (DAB)

The first product and current primary development focus. A high-performance asset and workflow infrastructure designed around Autodesk Maya.

PHASE 2

DEEVLA Tools & Plugins

After DAB, DEEVLA plans to develop additional artist productivity tools, workflow automation, pipeline utilities, specialized plugins, and technical workflow solutions for Maya users. One major direction is the DEEVLA Smart Modeling Toolkit, a context-aware modeling tool family built around topology, curvature, selection, symmetry, validation, and artist intent.

PHASE 3

DEEVLA IDE

Long-term vision: a native-feeling, deeply integrated development environment for Autodesk Maya, designed for building, running, testing, debugging, diagnosing, and managing Maya tools and workflows directly inside the DCC environment, with modern editing, Maya-aware intelligence, runtime context, and future AI-assisted development capabilities.

DEEVLA product roadmap from DAB to tools and plugins to DEEVLA IDE Click to Zoom
Product direction: DAB is the first product; additional tools and plugins extend the ecosystem; DEEVLA IDE is the longer-term development-platform vision.
Phase 2 — DEEVLA Tools & Plugins

DEEVLA Smart Modeling Toolkit — context-aware modeling tools for Maya.

After DAB, one of DEEVLA's major product directions is a family of focused Maya tools and plugins. A key concept is the DEEVLA Smart Modeling Toolkit: modeling operations that inspect topology, curvature, normals, selection context, symmetry, boundaries, and production intent before applying an operation. Rather than simply recreating existing Maya modeling commands, DEEVLA is exploring an intelligence layer around the modeling workflow — allowing familiar operations to evaluate context, identify better candidates, anticipate common topology problems, and make more informed decisions before execution. The goal is not to hide Maya, but to make repetitive modeling decisions faster, safer, and more context-aware while keeping the workflow lightweight and familiar to Maya artists.

Objective

Context-aware modeling

Move beyond one-command/one-result behavior by evaluating the current mesh and selection before suggesting or applying the most appropriate modeling operation.

Workflow

Reduce repetitive setup

Automate common preparation, cleanup, alignment, validation, topology checks, and repetitive parameter decisions so artists can spend more time on shape and design.

Direction

Procedural ideas, Maya-native feel

Bring selected procedural and context-driven ideas into Maya without trying to turn Maya into another DCC. Tools should remain fast, focused, undoable, predictable, and familiar to Maya users.

1. Smart Boolean
2. Smart Cleanup
3. Smart Topology Flow
4. Smart Selection
5. Smart Modeling Assistant

Priority package concept: Smart Boolean, Smart Cleanup, Smart Topology Flow, Smart Selection, and Smart Modeling Assistant can form the first focused subset of the DEEVLA Smart Modeling Toolkit. “Smart Cleanup” and “Smart Topology Flow” act as umbrella systems that combine several of the specialized analysis and repair ideas below.

Topology, Merge, Bridge, Fill & Surface Operations — 1 to 20
  1. Smart Merge — merge vertices using distance, surface direction, and topology context instead of a blind weld.
  2. Smart Bridge — determine correspondence, twist, segment count, and alignment when bridging two border regions.
  3. Smart Fill Hole — choose topology strategies such as quad-dominant, radial, grid, or planar caps based on the opening.
  4. Smart Extrude — extrude using curvature, normals, or chosen direction while maintaining more consistent thickness.
  5. Smart Inset — create visually consistent inset spacing on irregular face shapes.
  6. Smart Straighten — straighten vertices or edges while preserving surrounding form as much as possible.
  7. Smart Flatten — calculate a best-fit plane and flatten selected components to it.
  8. Smart Align — align vertices, edges, objects, pivots, or faces using likely alignment candidates from context.
  9. Smart Snap — context-aware snapping to vertices, midpoints, face centers, closest surfaces, projections, or normal-aware targets.
  10. Smart Pivot — derive useful pivots from center, base, selected face, hinge edge, symmetry plane, or mass-like context.
  11. Smart Thickness — generate more consistent shell thickness over curved surfaces.
  12. Smart Shell — create shells while detecting likely self-intersections and problematic regions.
  13. Smart Chamfer — preserve proportion while improving chamfer behavior around complex corners.
  14. Smart Corner — analyze bevel intersections and target cleaner corner topology.
  15. Smart Boolean — boolean workflow with cleanup, normal repair, coplanar detection, cutter management, and live/non-destructive direction.
  16. Smart Boolean Cutter — create and organize cutters from viewport-drawn shapes or selected geometry.
  17. Smart Hole Maker — click a surface to create circular, countersunk, screw, vent, or custom-profile holes.
  18. Smart Edge Loop — find a useful loop path using curvature/topology when a standard loop traversal is insufficient.
  19. Smart Loop Redirect — assist edge-flow direction changes using semi-automatic topology transitions.
  20. Smart Pole Manager — detect 3/5/6+ edge poles and suggest more appropriate positions for subdivision flow.
Mesh Quality, Subdivision, Normals & UV Intelligence — 21 to 35
  1. Smart Relax — relax geometry while preserving boundaries, silhouette, hard edges, UV constraints, and anchor vertices.
  2. Smart Smooth — add topology where curvature indicates it is actually needed.
  3. Smart Reduce — reduce polygons while protecting silhouette, hard edges, UV seams, and important detail.
  4. Smart Subdivision Preview — flag pinching, overly tight support loops, uneven topology, and problematic pole placement.
  5. Smart Pinch Detector — highlight areas likely to create subdivision artifacts.
  6. Smart Ngon Inspector — classify ngons by likely safety, deformation risk, subdivision risk, or shading risk.
  7. Smart Triangle Inspector — identify triangles that may create shading or deformation problems.
  8. Smart Normal — manage hard/soft edges and vertex normals using shape, angle, and curvature context.
  9. Smart Hard Edge — determine hard edges from actual form rather than relying only on a fixed angle threshold.
  10. Smart UV Seam — analyze object shape and suggest likely UV seam placement.
  11. Smart UV Straighten — straighten UV shells while preserving proportions as much as possible.
  12. Smart UV Density — normalize texel density across selected asset regions.
  13. Smart Mirror — detect a likely symmetry plane even when the object is not perfectly centered at world origin.
  14. Smart Symmetry Repair — compare left and right sides and repair vertices that have drifted away from symmetry.
  15. Smart Centerline — detect center vertices and return them accurately to the symmetry axis.
Cleanup, Validation, Deformation & Curve Workflows — 36 to 49
  1. Smart Gap Fix — find small unintended gaps between meshes or border regions that should connect.
  2. Smart Intersection Detector — detect mesh intersections and self-intersections.
  3. Smart Floating Geometry — identify small separated or abandoned pieces of geometry.
  4. Smart Duplicate Geometry — identify coincident faces, vertices, or duplicated overlapping meshes.
  5. Smart Scale Checker — validate asset dimensions against scene units or a production scale policy.
  6. Smart Proportion — help preserve proportions while scaling or reshaping parts of a model.
  7. Smart Bend — bend an object using inferred axis and pivot without repetitive manual deformer setup.
  8. Smart Taper — apply taper with axis and pivot derived from object form.
  9. Smart Deform Cage — generate a simple edit/deformation cage automatically for fast shaping.
  10. Smart Curve Extract — convert selected edges to clean curves with consistent direction and smoothing.
  11. Smart Curve Fit — fit a smoother curve to rough edge flow with a useful CV count.
  12. Smart Pipe — convert curves to pipes with orientation, thickness, caps, UVs, and corner handling.
  13. Smart Cable — create cable systems with sag, twist, connectors, and diameter variation.
  14. Smart Trim — place trim/profile geometry along edges or curves with reduced setup.
Procedural Detail, Export, Naming & Smart Selection — 50 to 60
  1. Smart Panel Line — create surface-following panel lines from selected or drawn paths.
  2. Smart Rivet — distribute rivets or bolts along edges using automatic spacing.
  3. Smart Detail Scatter — scatter small detail using curvature and exclusion rules.
  4. Smart Damage — procedural variation for dents, scratches, chips, and edge wear.
  5. Smart LOD Generator — build multiple levels of detail while prioritizing the primary silhouette.
  6. Smart Game Export Prep — one workflow for cleanup, transforms, pivots, naming, triangulation, UV checks, and export validation.
  7. Smart Naming — infer object type/context and apply naming based on hierarchy or production rules.
  8. Smart Selection — predict likely related components from the user's current selection and topology context.
  9. Smart Similar — find faces, edges, or objects with similar shape, area, scale, or curvature.
  10. Smart Pattern Select — detect repeating selection patterns such as every second edge, every third face, checker, or ring patterns.
  11. Smart Modeling Assistant — inspect current selection and show only context-relevant actions, e.g. two open edge borders → Bridge, Align Borders, Match Vertex Count, Close Gap.
Product direction: These concepts are a development roadmap, not a claim that all 60 tools are currently implemented. The toolkit will be developed incrementally after DAB, with priority given to operations that solve clear production pain points and can remain fast, predictable, and native-feeling inside Maya.
Phase 3 — Long-Term Vision

DEEVLA IDE — a deeply integrated development environment for Maya.

DEEVLA's longer-term platform vision is a native-feeling, deeply integrated IDE for Maya tool and pipeline development. Instead of forcing developers and technical artists to choose between Maya's built-in Script Editor and an external IDE that cannot fully understand the live scene, DEEVLA IDE is intended to combine a modern development experience with direct access to Maya's runtime, selection, scene state, commands, callbacks, and APIs.

Maya Script Editor

Excellent for immediate scripting and runtime access, but its role is intentionally lighter than a full modern development environment.

  • Direct Maya runtime access
  • Fast interactive execution
  • Limited large-project IDE workflow

External IDE

Powerful editing and project tooling, but live Maya context normally requires extra bridges, remote execution, or separate debugging setup.

  • Strong editing and navigation
  • Good project-scale development
  • Less direct awareness of the active Maya scene

DEEVLA IDE Direction

Bring modern development capabilities into a Maya-integrated workspace so code, runtime state, tool UI, output, diagnostics, and scene context can work together.

  • Runs docked / integrated inside Maya
  • Direct Python and MEL execution
  • Maya-aware scene and selection intelligence

Modern Code Editing

High-performance editor direction with syntax handling, multi-document workflows, search/replace, code navigation, command palette, shortcuts, sessions, and project/workspace organization.

Runtime-aware Intelligence

Planned completion, signatures, hover information, diagnostics, navigation, and code actions that can combine static source intelligence with Maya-specific runtime context.

Execution & Output

Direct Python/MEL document and selection execution, integrated output console, traceback/error handling, diagnostics, and faster iteration without constantly moving between Maya and another application.

Maya Context Awareness

The IDE can be designed to understand the active Maya version, scene, selection, host capabilities, commands, and tool context — information an ordinary external text editor does not automatically possess.

Tool & UI Development

Future direction includes reusable DEEVLA UI framework components, integrated tool development, visual Tool Designer concepts, and AI-assisted UI generation for Maya tools.

AI-native Development Direction

AI assistance is envisioned as part of the development workflow rather than only a chat panel: code/tool generation, diagnostics, contextual suggestions, refactoring support, and Maya-aware assistance can use project and runtime context when appropriate.

Why build it?
Maya developers frequently move between code editors, Script Editor output, Maya documentation, scene inspection, UI testing, and runtime debugging. A Maya-integrated IDE can reduce this context switching and make the development loop — write → run → inspect → diagnose → refine — significantly more direct.
Long-term status: DEEVLA IDE is a future platform direction after DAB and the initial tools/plugins roadmap. It is presented here to explain DEEVLA's longer-term Maya tool and pipeline development strategy, not as a currently released product.
Independent Development

Built independently.

DEEVLA is a fully independent development initiative founded on original ideas, research, and innovation. It is developed independently and is not affiliated with, sponsored by, or created on behalf of any external studio or company.

Autodesk Platform Services (APS)

Current APS status.

DEEVLA is not currently using Autodesk Platform Services (APS) APIs. The current development focus is direct desktop integration with Autodesk Maya. APS may be evaluated in the future only if a specific product requirement benefits from it.

Why ADN

Why DEEVLA is applying to the Autodesk Developer Network.

DEEVLA is applying to ADN to develop and validate Maya-integrated products in the appropriate Autodesk development environment and to gain access to the technical resources needed to build reliable, maintainable integration with Autodesk Maya.

Application Context: DEEVLA is an independent, founder-led initiative founded in August 2026, with one founder and zero employees. It is not part of an official startup/incubator program. The first product is DEEVLA Asset Browser (DAB), currently focused on direct Autodesk Maya desktop integration; Autodesk Platform Services (APS) APIs are not currently used.

Development & Testing

Access to the appropriate Autodesk Maya development and testing environment for building and validating DEEVLA products.

Documentation & Guidance

Developer documentation, API guidance, technical resources, and support for Autodesk Maya integration and compatibility.

Compatibility Validation

Testing DAB and future DEEVLA products across supported Autodesk Maya environments as the product evolves.

Intended ADN Use: Any Autodesk software, support, documentation, or other resources provided through ADN will be used solely for DEEVLA product development, testing, technical validation, demonstration, support, and marketing of products developed by DEEVLA. ADN resources will not be used for unrelated production modeling, design, drafting, client work, employment duties, or work performed for any employer, external studio, or other company.
Site-Based Membership / Development Location: DEEVLA understands that ADN membership is site-based. The current primary development location is Surabaya, East Java, Indonesia. Any Autodesk software, support, documentation, or other ADN resources approved for DEEVLA will be used only in accordance with the development location approved by Autodesk.
Founder & Contact

Founder contact and company correspondence.

DEEVLA is currently founder-led. For development, technical, product, partnership, or business correspondence, please use the contact information below.

Riyadus Solihin — Founder of DEEVLA

Riyadus Solihin

Founder — DEEVLA
Company Email
riyadus@deevla.com
Founder / Contact Location
Surabaya, East Java, Indonesia
Postal Code
60285