* Task procedures can be outlined in the same style as when using a traditional preemptive RTOS. * cocoOS is extremely portable to any target which makes it a perfect choice during early phases in the development when which OS to use is still an open issue. * cocoOS is released under a BSD license.

* System type - multithread, preemptive * Scheduler - maximum priority, fast context switch between threads, preemption may be blocked for specific part * Synchronization objects - mutex (nesting allowed), counting semaphore (may be signalled from ISR) * Timing control - timers, timeouts in semaphore waiting function, sleep function * Communication - ring buffers, effective implementation of queue, events * State machines - finite state machines support for coding behavior, unified events defined for commutication, active state machines manager that performs control over state machines * Memory management - memory pool, effective allocator, free of fragmentation issue * Debugging support - signalling events on chip pins (useful when tracking time dependencies and real time bugs), critical exceptions for unrecoverable bugs, deleted objects marking * Configuration - Many user configurable flags that affects compiled code of the system, User assigns processor resources that are used by the operating system